From: Andreas Schwab <schwab@linux-m68k.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tromey@redhat.com>, Jim Meyering <jim@meyering.net>,
gdb-patches@sourceware.org
Subject: Re: gdb_7_3-branch not buildable?
Date: Tue, 19 Apr 2011 16:16:00 -0000 [thread overview]
Message-ID: <m239lefc8x.fsf@igel.home> (raw)
In-Reply-To: <20110419150111.GA2601@adacore.com> (Joel Brobecker's message of "Tue, 19 Apr 2011 08:01:11 -0700")
Joel Brobecker <brobecker@adacore.com> writes:
>> > Andreas, could you say what you did to make yours better?
>>
>> Handcraft. These are things that something based on cvsps cannot do
>> better.
>
> Can we take your branch and force-push it?
The repositories are not compatible, mine is mirroring the whole src
repo, not just the gdb subset.
> If we could do that without confusing cvsps, that'd be awesome.
You can just reset the branch to the gdb-7.3 branchpoint, and
git-cvsimport will happily continue from that point.
(The gdb_7_3-2011-04-01-branchpoint tag is missing in the git repo,
since it was created in the past. It should be added to
c73dde705c3b163b5101ed4cc4506cef6cc58905.)
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-19 16:16 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
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 [this message]
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=m239lefc8x.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=brobecker@adacore.com \
--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