Re: [PATCH] Replace git-cvsimport with a rewrite that fixes major bugs.
- From
Martin Langhoff <martin.langhoff@gmail.com>
- Date
- Jan 2, 2013, 21:15 UTC
- Message-ID
- <CACPiFCKNkpaf6CgU=5rn1dyUSG2KV43oeTKJgRsSh9-Rhtq3Kw@mail.gmail.com>
- In-Reply-To
- <20130102164107.GA19006@thyrsus.com>
On Wed, Jan 2, 2013 at 11:41 AM, Eric S. Raymond <esr@thyrsus.com> wrote:
Show 6 quoted lines
> Martin Langhoff <martin.langhoff@gmail.com>: >> Replacement with something more solid is welcome, but until you are >> extremely confident of its handling of legacy setups... I would still >> provide the old cvsimport, perhaps in contrib. > > I am extremely confident. I built a test suite so I could be.
This is rather off-putting. Really.
I dealt with enough CVS repos to see that the branch point could be ambiguous, and that some cases were incurably ugly and ambiguous.
Off the top of my head I can recall
- Files created on a branch appear on HEAD (if the cvs client was well behaved, in HEAD's attic, if the cvs client was buggy... )
- Files tagged with the branch at a much later time. Scenario is a developer opening/tagging a new branch mindlessly on a partial checkout; then trying to "fix" the problem later.
My best guess is that you haven't dealt with enough ugly CVS repos. I used to have the old original X.org repos, but no more. Surely Mozilla's fugly old CVS repos are up somewhere, and may be therapeutic.
cheers,
m -- martin.langhoff@gmail.com martin@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff