From: Andreas Schwab <schwab@linux-m68k.org>
To: Jim Meyering <jim@meyering.net>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: gdb_7_3-branch not buildable?
Date: Sat, 16 Apr 2011 07:44:00 -0000 [thread overview]
Message-ID: <m2oc467i9t.fsf@igel.home> (raw)
In-Reply-To: <878vvbkv3r.fsf@rho.meyering.net> (Jim Meyering's message of "Sat, 16 Apr 2011 00:28:24 +0200")
Jim Meyering <jim@meyering.net> writes:
> That's many more differences than I expected,
> so maybe something is going wrong with the mirroring
> mechanism (note that git's top-level ChangeLog has four
> commits from april 4 that are not in git-cvs's ChangeLog file).
git-cvsimport can easily be confused by a branch that is created from a
point back in time. That's a fundamental restriction of cvsps, because
it only tells you about the revision of files that changed on the
branch, but you never know the revision of the files that are unchanged.
To fix that you have to manually reset the branch to the true
branchpoint. See <git://repo.or.cz/src> for a more precise rendition of
the src repository.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2011-04-16 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 22:29 Jim Meyering
2011-04-16 7:44 ` Andreas Schwab [this message]
2011-04-17 1:38 ` Joel Brobecker
2011-04-18 16:56 ` Tom Tromey
2011-04-18 17:47 ` Andreas Schwab
2011-04-19 15:01 ` Joel Brobecker
2011-04-19 16:16 ` Andreas Schwab
2011-05-03 10:51 ` Jim Meyering
2011-05-03 13:10 ` Andreas Schwab
2011-05-03 13:32 ` Jim Meyering
2011-05-03 13:50 ` Andreas Schwab
2011-05-03 14:37 ` Jim Meyering
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=m2oc467i9t.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gdb-patches@sourceware.org \
--cc=jim@meyering.net \
--cc=tromey@redhat.com \
/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