[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn modules (was Re: Features and release dates)

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-05-02 18:54:46 CEST

Zack Weinberg <zack@codesourcery.com> writes:

> So suppose I lay out the merged repository like so:
> repo/complete/gcc
> gdb
> binutils
> libiberty
> ...
> gcc/trunk/gcc == ../../../complete/gcc
> libiberty == ../../../complete/libiberty
> gdb/trunk/gdb == ../../../complete/gdb
> libiberty == ../../../complete/libiberty
> Then I want to be able to 'svn cp' gcc/trunk to gcc/3.1-branch, check
> in patches to gcc/3.1/gcc/whatever.c, and have whatever.c record a
> proper branch in its per-file history.
> I also want to be able to check out repo/gcc/3.1.0-release,
> repo/gdb/5.1.1-release, repo/binutils/2.12.4-release, all into the
> same directory, have something sensible happen with files that are
> shared between the threee, and then do "svn up" later and have each
> subset of files track the branch it was checked out from. You try
> this with CVS and directories that are shared between the branches
> tend to get confused which branch you want them on.

Well, Subversion doesn't support checking-out multiple URLs into the
same directory. So you can't do

   svn co .../repo/gcc/3.1.0-release -d wc/
   svn co .../repo/gdb/5.1.1-release -d wc/

I don't know if there are any plans to change this. The admin file
wc/.svn/entries stores the URL used to checkout the directory, and at
present Subversion pretty much assumes that the directory has a single

You may be able to use the switch command to get what you want,
something like

   svn co .../repo/complete -d wc/
   cd wc/gcc
   svn switch .../repo/3.1.0-release
   cd ../gdb
   svn switch .../repo/5.1.1-release


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 2 18:55:41 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.