From: Daniel Jacobowitz <drow@false.org>
To: Paul Koning <pkoning@equallogic.com>
Cc: paul@codesourcery.com, binutils@sourceware.org, jbglaw@lug-owl.de
Subject: Re: svn read of the binutils development repository?
Date: Wed, 12 Apr 2006 15:12:00 -0000 [thread overview]
Message-ID: <20060412140210.GC23288@nevyn.them.org> (raw)
In-Reply-To: <17469.1894.372810.524042@gargle.gargle.HOWL>
On Wed, Apr 12, 2006 at 09:57:58AM -0400, Paul Koning wrote:
> Externals can do this.
Externals offer their own host of problems. Off the top of my head,
you have to use a more complicated procedure to create branches,
you have to take a different approach to use SVK, and I believe
commits won't recurse properly if you want to change both bfd and
gdb. And you can't readily use externals to get individual
files, like those in the top level.
I've spent quite a lot of time working on this problem; I don't
think externals are a satisfactory solution.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-12 14:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 18:26 Christian Joensson
2006-04-10 15:44 ` Daniel Jacobowitz
2006-04-11 23:57 ` Ben Elliston
2006-04-12 6:06 ` Daniel Jacobowitz
2006-04-12 6:40 ` Jan-Benedict Glaw
2006-04-12 13:47 ` Paul Brook
2006-04-12 13:55 ` Paul Koning
2006-04-12 13:58 ` Daniel Jacobowitz
2006-04-12 13:58 ` Paul Koning
2006-04-12 15:12 ` Daniel Jacobowitz [this message]
2006-04-12 14:02 ` Daniel Jacobowitz
2006-05-09 14:17 ` Christian Joensson
2006-05-09 14:49 ` Daniel Jacobowitz
2006-08-08 14:31 ` Christian Joensson
2006-08-08 14:52 ` Daniel Jacobowitz
2006-08-08 16:59 ` Daniel Jacobowitz
2006-11-23 11:14 ` Christian Joensson
2006-04-12 13:05 Alessio.MASSARO
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=20060412140210.GC23288@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.org \
--cc=jbglaw@lug-owl.de \
--cc=paul@codesourcery.com \
--cc=pkoning@equallogic.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).