* Keeping binutils/{bfd, opcodes} and gdb/{bfd, opcodes} in synch.
@ 2007-06-13 20:24 Anmol P. Paralkar
2007-06-13 20:40 ` Daniel Jacobowitz
0 siblings, 1 reply; 2+ messages in thread
From: Anmol P. Paralkar @ 2007-06-13 20:24 UTC (permalink / raw)
To: gdb
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).
Thanks,
Anmol.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Keeping binutils/{bfd, opcodes} and gdb/{bfd, opcodes} in synch.
2007-06-13 20:24 Keeping binutils/{bfd, opcodes} and gdb/{bfd, opcodes} in synch Anmol P. Paralkar
@ 2007-06-13 20:40 ` Daniel Jacobowitz
0 siblings, 0 replies; 2+ messages in thread
From: Daniel Jacobowitz @ 2007-06-13 20:40 UTC (permalink / raw)
To: Anmol P. Paralkar; +Cc: gdb
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-06-13 20:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-06-13 20:24 Keeping binutils/{bfd, opcodes} and gdb/{bfd, opcodes} in synch Anmol P. Paralkar
2007-06-13 20:40 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox