On 03.01.2013, at 21:53, Eric S. Raymond wrote: > Michael Haggerty <mhagger@xxxxxxxxxxxx>: >> 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. > > They are *not* good reasons for having an interface that exposes this > implementation detail to the caller - that choice I consider a failure > of interface-design judgment. But I know how to fix this in a simple and > backward-compatible way, and will do so when I have time to write you > a patch. Next week or the week after, most likely. > > Also, the cvs2git manual page is still rather half-baked and careless, > with several fossil references to cvs2svn that shouldn't be there and > obviously incomplete feature coverage. Fixing these bugs is also on my > to-do list for sometime this month. > > I'd be willing to put in this work anyway, but it still in the back of > my mind that if cvs2git wins the test-suite competition I might > officially end-of-life both cvsps and parsecvs. One of the features > of the new git-cvsimport is direct support for using cvs2git as a > conversion engine. > >> A potentially bigger problem is that if you want to handle such >> blob/dump output, you have to deal with git-fast-import format's "blob" >> command as opposed to only handling inline blobs. > > Not a problem. All of the main potential consumers for this output, > including reposurgeon, handle the blob command just fine. 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 call "hg fast-import" a main potential customer, given that there "cvs2hg" is another part of the cvs2svn suite. So I can't quite see how you can come to your conclusion above... Cheers, Max-- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html