From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gdb ml <gdb@sourceware.org>
Subject: Re: incomplete binutils patch in gdb
Date: Mon, 02 Mar 2009 13:54:00 -0000 [thread overview]
Message-ID: <1236002047.8949.58.camel@localhost.localdomain> (raw)
In-Reply-To: <m2prh2qzcr.fsf@igel.home>
El sáb, 28-02-2009 a las 17:51 +0100, Andreas Schwab escribió:
> 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.)
Indeed, I checked out the GDB CVS tree again, and things are normal
there.
But the GDB git mirror has the same problem that my old CVS checkout
had. In fact, that's why I didn't think it was a problem with my CVS
checkout. Perhaps this is some weird limitation of CVS when doing
updates? I don't know...
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
prev parent reply other threads:[~2009-03-02 13:54 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
2009-03-02 13:54 ` Thiago Jung Bauermann [this message]
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=1236002047.8949.58.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=gdb@sourceware.org \
--cc=schwab@linux-m68k.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