From: Daniel Jacobowitz <drow@false.org>
To: Richard Earnshaw <rearnsha@arm.com>
Cc: gdb@sourceware.org, Samuel Bronson <naesten@gmail.com>
Subject: Re: What is keeping GDB in CVS ?
Date: Fri, 19 Jun 2009 17:28:00 -0000 [thread overview]
Message-ID: <20090619172848.GA18945@caradoc.them.org> (raw)
In-Reply-To: <1245430587.11675.47.camel@pc960.cambridge.arm.com>
On Fri, Jun 19, 2009 at 05:56:27PM +0100, Richard Earnshaw wrote:
> As someone who builds complete cross toolchains on a regular basis, I'd
> prefer for things not to become too fragmented. My preferred split
> would be for those tools that share source infrastructure to remain
> combined (binutils/gas/gdb) and maybe split out the others. It would be
> a right royal pain to have to edit three copies of an identical file
> when developing and testing -- it's bad enough having gcc outside of the
> infrastructure.
FWIW, I see this as a problem we could solve with scripts and/or docs;
I've done this using symlinks to binutils plenty of times.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-06-19 17:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 16:13 Samuel Bronson
2009-06-19 16:23 ` Daniel Jacobowitz
2009-06-19 16:28 ` Daniel Jacobowitz
2009-06-19 16:38 ` Christopher Faylor
2009-06-19 16:49 ` Daniel Jacobowitz
2009-06-19 16:56 ` Richard Earnshaw
2009-06-19 17:28 ` Daniel Jacobowitz [this message]
2009-06-19 17:30 ` Tom Tromey
2009-06-19 19:18 ` Joseph S. Myers
2009-06-19 17:18 ` Joseph S. Myers
2009-06-19 19:22 ` Christopher Faylor
2009-06-19 19:29 ` Joseph S. Myers
2009-06-20 18:48 ` Christopher Faylor
2009-06-20 19:19 ` Joseph S. Myers
2009-06-20 20:36 ` Christopher Faylor
2009-06-20 20:53 ` Jan Kratochvil
2009-06-25 21:45 ` Tom Tromey
2009-06-26 12:28 ` Daniel Jacobowitz
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=20090619172848.GA18945@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=naesten@gmail.com \
--cc=rearnsha@arm.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