From: Paul Koning <pkoning@equallogic.com>
To: paul@codesourcery.com
Cc: binutils@sourceware.org, jbglaw@lug-owl.de
Subject: Re: svn read of the binutils development repository?
Date: Wed, 12 Apr 2006 13:55:00 -0000 [thread overview]
Message-ID: <17469.1254.661785.22130@gargle.gargle.HOWL> (raw)
In-Reply-To: <200604121409.05845.paul@codesourcery.com>
>>>>> "Paul" == Paul Brook <paul@codesourcery.com> writes:
>> IBGT on the `check out just binutils' thing: HDDs are somewhat
>> cheap these days and thus I'd just rule out that argument.
Paul> It's not just disk space, it's also network bandwidth. The
Paul> entire src tree is three times the size of just binutils (340Mb
Paul> vs 113Mb).
Paul> Also if you have a fully populated src tree toplevel configure
Paul> will try and build all of it. Getting all of gdb, newlib,
Paul> cygwin and GOK what else when you just want binutils doesn't
Paul> sound like a practical solution.
Sure. But I don't understand the statement that Subversion doesn't
support doing so -- it does. You can check out any subtree you want.
paul
next prev parent reply other threads:[~2006-04-12 13:47 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 [this message]
2006-04-12 13:58 ` Daniel Jacobowitz
2006-04-12 13:58 ` Paul Koning
2006-04-12 15:12 ` Daniel Jacobowitz
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=17469.1254.661785.22130@gargle.gargle.HOWL \
--to=pkoning@equallogic.com \
--cc=binutils@sourceware.org \
--cc=jbglaw@lug-owl.de \
--cc=paul@codesourcery.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).