Re: [Monotone-devel] cvssync branch feedback

2005-05-26 Thread Lele Gaifax
> "Matt" == Matt Lavin <[EMAIL PROTECTED]> writes: Matt> I'll try to clear up some of my statements. Thank you, appreciated! Matt> 1. ... For the tailor.py build project I had a couple of Matt> extra empty directories and 1 missing file. One thing I Matt> noticed about the

Re: [Monotone-devel] cvssync branch feedback

2005-05-25 Thread Matt Lavin
I hope I didn't appear to be slamming tailor.py, I was trying mostly to compliment cvssync. I'll try to clear up some of my statements. 1. "correct file generation" should have been "correct directory contents". I have a rather large project that I was trying to convert ( ~3500 patches) and

Re: [Monotone-devel] cvssync branch feedback

2005-05-25 Thread Lele Gaifax
> "Matt" == Matt Lavin <[EMAIL PROTECTED]> writes: Matt> If you are targeting monotone as the new SCM then cvssync is Matt> heads above tailor.py in terms of speed and correct file Matt> generation. No doubt on former, given the different overall goals of the two, but I'd like to

[Monotone-devel] cvssync branch feedback

2005-05-25 Thread Matt Lavin
Let me start by saying that the cvssync branch is the best CVS history preserving converter I have used. If you are targeting monotone as the new SCM then cvssync is heads above tailor.py in terms of speed and correct file generation. I got exactly what I wanted from the cvssync branch in alm