From: Andreas Schwab <schwab@linux-m68k.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb ml <gdb@sourceware.org>
Subject: Re: incomplete binutils patch in gdb
Date: Sat, 28 Feb 2009 16:51:00 -0000 [thread overview]
Message-ID: <m2prh2qzcr.fsf@igel.home> (raw)
In-Reply-To: <1235770116.8949.44.camel@localhost.localdomain> (Thiago Jung Bauermann's message of "Fri, 27 Feb 2009 18:28:36 -0300")
Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
> is incomplete in GDB CVS. It misses the changes in ppc-opc.c. I checked
> out binutils CVS and it's fine there. Does anyone know what's going on?
The gdb and binutils repositories are one and the same. Are you sure
you haven't accidentally set a sticky tag? (Use cvs up -A to reset it.)
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-02-28 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 21:28 Thiago Jung Bauermann
2009-02-28 16:51 ` Andreas Schwab [this message]
2009-03-02 13:54 ` Thiago Jung Bauermann
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=m2prh2qzcr.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=bauerman@br.ibm.com \
--cc=gdb@sourceware.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