From: Andrew STUBBS <andrew.stubbs@st.com>
To: binutils@sourceware.org
Subject: Re: SVN for src (was Re: Binutils 2.18 prep)
Date: Thu, 22 Mar 2007 15:35:00 -0000 [thread overview]
Message-ID: <4602A20D.7020207@st.com> (raw)
In-Reply-To: <20070322150018.GA4566@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Thu, Mar 22, 2007 at 10:06:41AM +0000, Andrew STUBBS wrote:
>> We create an Subversion directory containing all the top-level files (configure
>> etc.), but with all the subdirectories (gas, gdb etc.) present but *empty*. We
>> then provide a script that does 'svn switch' on each directory required for a
>> given 'module'. This is the inverse of the svn://gcc.gnu.org/svn/gcc/emptydir
>> idea (see http://gcc.gnu.org/wiki/SvnSetup "Optimize disk usage").
>
> You know, I think we can do this even without having to butcher the
> layout of the repository. Check out a directory containing just the
> script, and have it use "svn switch -N" at the end to pick up the top
> level files.
>
> I'm going to experiment. I have a handy repository to work with :-)
> (We import CVS snapshots into svn.)
Magic, it works!
I did originally think about doing 'svn co -N src', but that makes it
impossible to get at the subdirectories at all (another checkout works,
but then you can't check in properly).
I hadn't though of pulling in the root via switch. Nice idea.
So we would have:
svn co svn://sourceware.org/svn/trunk/modular-checkout src
cd src
./checkout binutils
which would then do:
svn switch svn://sourceware.org/svn/trunk/src/binutils binutils
svn switch svn://sourceware.org/svn/trunk/src/gas gas
...
svn switch -N svn://sourceware.org/svn/trunk/src .
where the last line switches in the top level files, and switches out
the checkout script itself.
Anybody wanting to checkout *everything* still can, without jumping
through hoops!
I suppose that, given the -N switch, it is even possible to selectively
choose subdirectories (such as include/elf), as long as the empty
version already exists, thus:
svn switch -N svn://sourceware.org/svn/trunk/src/include include
svn switch svn://sourceware.org/svn/trunk/src/include/elf \
include/elf
I can't think of any way to select individual files.
Andrew
next prev parent reply other threads:[~2007-03-22 15:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 2:48 Binutils 2.18 prep Daniel Jacobowitz
2007-03-22 10:06 ` SVN for src (was Re: Binutils 2.18 prep) Andrew STUBBS
2007-03-22 10:45 ` Diego 'Flameeyes' Pettenò
2007-03-22 11:06 ` Andrew STUBBS
2007-03-22 11:23 ` Diego 'Flameeyes' Pettenò
2007-03-22 14:07 ` Paul Brook
2007-03-22 14:20 ` Andrew STUBBS
2007-03-22 14:31 ` Joseph S. Myers
2007-03-22 14:11 ` Bob Rossi
2007-03-22 14:17 ` Daniel Jacobowitz
2007-03-22 15:00 ` Daniel Jacobowitz
2007-03-22 15:28 ` Daniel Jacobowitz
2007-03-22 15:51 ` Andrew STUBBS
2007-03-26 14:59 ` Daniel Jacobowitz
2007-03-26 16:32 ` Andrew STUBBS
2007-04-10 17:25 ` Daniel Jacobowitz
2007-04-11 10:22 ` Andrew STUBBS
2007-04-11 11:06 ` Daniel Jacobowitz
2007-04-11 13:46 ` Paul Koning
2007-04-11 14:18 ` Ian Lance Taylor
2007-04-11 15:00 ` Daniel Jacobowitz
2007-04-11 15:23 ` Ian Lance Taylor
2007-03-22 15:35 ` Andrew STUBBS [this message]
2007-03-22 16:48 ` DJ Delorie
2007-03-22 17:08 ` Andrew STUBBS
2007-03-22 18:15 ` DJ Delorie
2007-03-23 9:12 ` Andrew STUBBS
2007-03-26 14:57 ` Daniel Jacobowitz
2007-03-26 15:16 ` Daniel Jacobowitz
2007-07-30 18:09 ` Binutils 2.18 prep Daniel Jacobowitz
2007-07-30 18:14 ` H.J. Lu
2007-08-01 17:57 ` Jim Wilson
2007-08-02 0:08 ` l l
2007-08-06 21:13 ` Daniel Jacobowitz
2007-08-07 8:18 ` Add bfin-*rtems* [was: Binutils 2.18 prep] Ralf Corsepius
2007-08-07 9:33 ` Nick Clifton
2007-08-09 11:45 ` Binutils 2.18 prep Matthias Klose
2007-08-13 0:33 ` 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=4602A20D.7020207@st.com \
--to=andrew.stubbs@st.com \
--cc=binutils@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).