git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: David Mansfield <david@cobite.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] cvsps/cvsimport: fix branch point calculation and broken branch imports
Date: Wed, 02 Apr 2008 12:29:17 -0700	[thread overview]
Message-ID: <7vprt8838y.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1207100091.10532.64.camel@gandalf.cobite.com> (David Mansfield's message of "Tue, 01 Apr 2008 21:34:51 -0400")

David Mansfield <david@cobite.com> writes:

> In case you're wondering, I'm actually the original author of cvsps,
> which is behind the scenes for cvsimport.  I don't call myself
> maintainer because I've hardly been that over the last few years.
>
> Anyway, the fix to cvsps is attached (1st 2 patches) as well as the
> patch to git-cvsimport.perl (2nd 2 patches) against the master branch as
> of today's git repo.
>
> The cvsps patches apply with fuzz against the 2.1 version which is out
> there.

When output from an unfixed cvsps is fed to the updated cvsimport, does it
gracefully do the wrong thing (iow, create the same broken history not too
much worse than the original)?

> @@ -826,12 +824,9 @@ while (<CVS>) {
>  		$branch = $_;
>  		$state = 5;
>  	} elsif ($state == 5 and s/^Ancestor branch:\s+//) {
> -		s/\s+$//;
> -		$ancestor = $_;
> -		$ancestor = $opt_o if $ancestor eq "HEAD";
> +		# now ignored.  see 'Branches' below
>  		$state = 6;
>  	} elsif ($state == 5) {
> -		$ancestor = undef;
>  		$state = 6;
>  		redo;
>  	} elsif ($state == 6 and s/^Tag:\s+//) {

  reply	other threads:[~2008-04-02 19:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02  1:34 [PATCH] cvsps/cvsimport: fix branch point calculation and broken branch imports David Mansfield
2008-04-02 19:29 ` Junio C Hamano [this message]
2008-04-03  1:44   ` David Mansfield
2008-04-03  2:06     ` Junio C Hamano
2008-04-03  2:27       ` David Mansfield
2008-04-03  5:47 ` Steffen Prohaska
2008-04-03 13:49   ` David Mansfield
2008-04-04  9:52     ` Michael Haggerty
2008-04-07 17:54       ` David Mansfield
2008-04-07 18:07         ` Jean-François Veillette
2008-04-09  1:53         ` Michael Haggerty
2008-04-27  5:06           ` Ping Yin
2008-04-27  5:47             ` Michael Haggerty
2008-04-27  5:51               ` Ping Yin
2008-04-27  7:38                 ` Ping Yin
2008-04-27  7:43                   ` Ping Yin
2008-04-27  7:48                   ` Ping Yin
2008-04-27  8:48                     ` Ping Yin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vprt8838y.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=david@cobite.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).