[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-devel] Re: cvs import
From: |
Michael Haggerty |
Subject: |
[Monotone-devel] Re: cvs import |
Date: |
Thu, 14 Sep 2006 19:01:20 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060728 Thunderbird/1.5.0.5 Mnenhy/0.7.4.666 |
Jon Smirl wrote:
> On 9/14/06, Jakub Narebski <address@hidden> wrote:
>> Shawn Pearce wrote:
>>
>> > Originally I wanted Jon Smirl to modify the cvs2svn (...)
>>
>> By the way, will cvs2git (modified cvs2svn) and git-fast-import publicly
>> available?
>
> It has some unresolved problems so I wasn't spreading it around everywhere.
>
> It is based on cvs2svn from August. There has been too much change to
> the current cvs2svn to merge it anymore. [...]
>
> If the repo is missing branch tags cvs2svn may turn a single missing
> branch into hundreds of branches. The Mozilla repo has about 1000
> extra branches because of this.
[To explain to our studio audience:] Currently, if there is an actual
branch in CVS but no symbol associated with it, cvs2svn generates branch
labels like "unlabeled-1.2.3", where "1.2.3" is the branch revision
number in CVS for the particular file. The problem is that the branch
revision numbers for files in the same logical branch are usually
different. That is why many extra branches are generated.
Such unnamed branches cannot reasonably be accessed via CVS anyway, and
somebody probably made the conscious decision to delete the branch from
CVS (though without doing it correctly). Therefore such revisions are
probably garbage. It would be easy to add an option to discard such
revisions, and we should probably do so. (In fact, they can already be
excluded with "--exclude=unlabeled-.*".) The only caveat is that it is
possible for other, named branches to sprout from an unnamed branch. In
this case either the second branch would have to be excluded too, or the
unlabeled branch would have to be included.
Alternatively, there was a suggestion to add heuristics to guess which
files' "unlabeled" branches actually belong in the same original branch.
This would be a lot of work, and the result would never be very
accurate (for one thing, there is no evidence of the branch whatsoever
in files that had no commits on the branch).
Other ideas are welcome.
Michael
- [Monotone-devel] Re: cvs import, (continued)
- [Monotone-devel] Re: cvs import, Michael Haggerty, 2006/09/14
- [Monotone-devel] Re: cvs import, Jon Smirl, 2006/09/14
- [Monotone-devel] Re: cvs import, Martin Langhoff, 2006/09/14
- [Monotone-devel] Re: cvs import, Markus Schiltknecht, 2006/09/13
- [Monotone-devel] Re: cvs import, Jon Smirl, 2006/09/13
- [Monotone-devel] Re: cvs import, Michael Haggerty, 2006/09/14
- [Monotone-devel] Re: cvs import, Shawn Pearce, 2006/09/14
- [Monotone-devel] Re: cvs import, Jakub Narebski, 2006/09/14
- [Monotone-devel] Re: cvs import, Shawn Pearce, 2006/09/14
- [Monotone-devel] Re: cvs import, Jon Smirl, 2006/09/14
- [Monotone-devel] Re: cvs import,
Michael Haggerty <=
- [Monotone-devel] Re: cvs import, Jakub Narebski, 2006/09/14
- [Monotone-devel] Re: cvs import, Jon Smirl, 2006/09/14
- Re: [Monotone-devel] Re: cvs import, Nathaniel Smith, 2006/09/14
- [Monotone-devel] Re: cvs import, Markus Schiltknecht, 2006/09/15
- [Monotone-devel] Re: cvs import, Shawn Pearce, 2006/09/15
- [Monotone-devel] Re: cvs import, Oswald Buddenhagen, 2006/09/16
- Re: [Monotone-devel] Re: cvs import, Nathaniel Smith, 2006/09/16
Re: [Monotone-devel] cvs import, Nathaniel Smith, 2006/09/13