On 8/7/06, Jakub Narebski <jnareb@xxxxxxxxx> wrote:
Jon Smirl wrote: > How about sending out a stream of add/change/delete operations > interspersed with commits? That would let fast-import track the tree > and only generate tree nodes when they change. The problem with CVS, which cvsps (CVS PatchSet) tries to address is that changes are to a file, and reconstructing which changes go together to make _one_ commit...
The cvs2svn code is also gathering CVS commits into change sets. The advantage of the cvs2svn code is that it is written by some of the original CVS developers. Those developers are familiar with the 1,000 different ways to break a CVS repository and cvs2svn tries to deal with the breakage. cvsps works for some repositories but it fails on the Mozilla one. There is something about branches in the Mozilla repository that confuses it. cvs2svn handles the Mozilla repository correctly as far as I can tell. -- Jon Smirl jonsmirl@xxxxxxxxx - : 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