From: Daniel Jacobowitz <drow@false.org>
To: "Anmol P. Paralkar" <b07584@freescale.com>
Cc: gdb@sourceware.org
Subject: Re: Keeping binutils/{bfd, opcodes} and gdb/{bfd, opcodes} in synch.
Date: Wed, 13 Jun 2007 20:40:00 -0000 [thread overview]
Message-ID: <20070613204046.GA8474@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0706131513560.9640@ld0159-tx32.am.freescale.net>
On Wed, Jun 13, 2007 at 03:24:25PM -0500, Anmol P. Paralkar wrote:
> Hello,
>
> What is the general methodology for keeping the gdb/{opcodes, bfd, ...} and
> binutils/{opcodes, bfd, ...} in synch with each other? Is there some
> "synch policy" that GDB development follows? (I see quite a differential
> between these in gdb-6.6 and binutils-2.17).
That's because they weren't released at the same time, of course! The
two projects share a common CVS repository; their copies are exactly
the same.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-06-13 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 20:24 Anmol P. Paralkar
2007-06-13 20:40 ` Daniel Jacobowitz [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=20070613204046.GA8474@caradoc.them.org \
--to=drow@false.org \
--cc=b07584@freescale.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