Re: cvsps, parsecvs, svn2git and the CVS exporter mess

2013-01-06 Thread Michael Haggerty
On 01/05/2013 04:11 PM, Eric S. Raymond wrote: Perhaps I was unclear. I consider the interface design error to be not in the fact that all the blobs are written first or detached, but rather that the implementation detail of the two separate journal files is ever exposed. I understand why

Re: cvsps, parsecvs, svn2git and the CVS exporter mess

2013-01-05 Thread Max Horn
On 03.01.2013, at 21:53, Eric S. Raymond wrote: Michael Haggerty mhag...@alum.mit.edu: There are two good reasons that the output is written to two separate files: Those are good reasons to write to a pair of tempfiles, and I was able to deduce in advance most of what your explanation

Re: cvsps, parsecvs, svn2git and the CVS exporter mess

2013-01-05 Thread Eric S. Raymond
Max Horn post...@quendi.de: Hm, you snipped this part of Michael's mail: However, if that is a problem, it is possible to configure cvs2git to write the blobs inline with the rest of the dumpfile (this mode is supported because hg fast-import doesn't support detached blobs). I would

Re: cvsps, parsecvs, svn2git and the CVS exporter mess

2013-01-05 Thread Eric S. Raymond
Bart Massey b...@cs.pdx.edu: I don't know what Eric Raymond officially end-of-life-ing parsecvs means? You and Keith handed me the maintainer's baton. If I were to EOL it, that would be the successor you two designated judging in public that the code is unsalvageable or has become pointless.

Re: cvsps, parsecvs, svn2git and the CVS exporter mess

2013-01-05 Thread Jonathan Nieder
Eric S. Raymond wrote: Michael Haggerty wants me to trust that cvs2git's analysis stage has been fixed, but I must say that is a more difficult leap of faith when two of the most visible things about it are still (a) a conspicuous instance of interface misdesign, and (b) documentation that is

Re: cvsps, parsecvs, svn2git and the CVS exporter mess

2013-01-03 Thread Eric S. Raymond
Michael Haggerty mhag...@alum.mit.edu: There are two good reasons that the output is written to two separate files: Those are good reasons to write to a pair of tempfiles, and I was able to deduce in advance most of what your explanation would be from the bare fact that you did it that way.

Re: cvsps, parsecvs, svn2git and the CVS exporter mess

2012-12-23 Thread Heiko Voigt
Hi, On Sat, Dec 22, 2012 at 12:36:48PM -0500, Eric S. Raymond wrote: If we can agree on this, I'll start a public repo, and contribute my Python framework - it's more capable than any of the shell harnesses out there because it can easily drive interleaved operations on multiple checkout

Re: cvsps, parsecvs, svn2git and the CVS exporter mess

2012-12-23 Thread Eric S. Raymond
Heiko Voigt hvo...@hvoigt.net: Please share so we can have a look. BTW, where can I find your cvsps code? https://gitorious.org/cvsps Developments of the last 48 hours: 1. Andreas Schwab sent me a patch that uses commitids wherever the history has them - this makes all the time-skew