public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: overseers@sourceware.org, nickc@redhat.com
Subject: Re: Subversion and sources.redhat.com
Date: Thu, 03 Nov 2005 16:41:00 -0000	[thread overview]
Message-ID: <20051103155724.GA540@nevyn.them.org> (raw)
In-Reply-To: <20051103155455.GA396@nevyn.them.org>

On Thu, Nov 03, 2005 at 10:54:55AM -0500, Daniel Jacobowitz wrote:
> On Thu, Nov 03, 2005 at 07:31:58AM -0800, Ian Lance Taylor wrote:
> > It would probably be appropriate for their to be some coordination
> > among the projects who share the src repository (binutils, gdb,
> > cygwin, newlib).
> 
> Absolutely.  I'd like everyone to change at once.  Two things to note:
> 
>   - Some of the GDB developers seem opposed.  I'm not real clear on
>     why.
> 
>   - It might be nice to convert each project into its own svn
>     repository, and make use of svn:externals.  I'm not sure if it's
>     adequately flexible though.
> 
> The likely problem is that checking out less than the whole repository
> in Subversion is much more awkward.  I don't want to have to check out
> sid to build binutils.  Someone who cares about making the switch needs
> to sit down and play with the options.

No, svn:externals won't be a good fix for this problem; one is still
needed.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-11-03 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 15:03 Nick Clifton
2005-11-01 20:20 ` Ian Lance Taylor
2005-11-03 15:55   ` Nick Clifton
2005-11-03 15:57     ` Ian Lance Taylor
2005-11-03 16:14       ` Daniel Jacobowitz
2005-11-03 16:41         ` Daniel Jacobowitz [this message]
2005-11-03 20:19           ` Joseph S. Myers

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=20051103155724.GA540@nevyn.them.org \
    --to=drow@false.org \
    --cc=nickc@redhat.com \
    --cc=overseers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).