Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Cc: Samuel Bronson <naesten@gmail.com>
Subject: Re: What is keeping GDB in CVS ?
Date: Fri, 19 Jun 2009 16:49:00 -0000	[thread overview]
Message-ID: <20090619164943.GA16137@caradoc.them.org> (raw)
In-Reply-To: <20090619163753.GA9700@ednor.casa.cgf.cx>

On Fri, Jun 19, 2009 at 12:37:53PM -0400, Christopher Faylor wrote:
> I still think that the various projects merged under the "src" umbrella
> should be pulled apart and given their own repositories.  There is
> really, for instance, no reason for Cygwin or cgen, which are non-FSF
> projects, to be intermingled with gdb and binutils.
> 
> However, I am very sympathetic to the notion that "It ain't broke..."

The solution I'd like best, I think, is one with separate projects
that makes it easy to manually or automatically sync revisions from
the shared directories.  This may be nothing more than some clever
push hooks, for instance to reject manual changes to bfd/ being pushed
to the central gdb repository and to automatically propogate changes
to bfd/ from binutils.  Anyone feeling inspired enough to build a
proof-of-concept?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-06-19 16:49 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 [this message]
2009-06-19 16:56         ` Richard Earnshaw
2009-06-19 17:28           ` Daniel Jacobowitz
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=20090619164943.GA16137@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=naesten@gmail.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