This is the mail archive of the
mailing list for the GCC project.
Re: Moving C to its own directory (was Re: ObjC tree inlining)
- From: Zack Weinberg <zack at codesourcery dot com>
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Cc: Branko ?ibej <brane at xbc dot nu>, Phil Edwards <pedwards at disaster dot jaj dot com>,Neil Booth <neil at daikokuya dot demon dot co dot uk>, gcc at gcc dot gnu dot org,dev at subversion dot tigris dot org
- Date: Wed, 21 Nov 2001 15:33:31 -0800
- Subject: Re: Moving C to its own directory (was Re: ObjC tree inlining)
- References: <3BFBE544.email@example.com> <Pine.LNX.firstname.lastname@example.org>
On Wed, Nov 21, 2001 at 11:15:54PM +0000, Joseph S. Myers wrote:
> Can the Subversion version model handle multiple past development
> mainlines merging into one future mainline?
> We have at present the separate "gcc" and "src" repositories, which share
> some files - and some people would like to merge these into a single
> repository, but it would be desirable still to be able to check out either
> past tree on any tag or date from before the merge.
There's a related problem, which we have now with CVS in the src
repository, but would get worse if they were merged. CVS does not
remember which module(s) you originally selected when you checked out
a tree. Therefore, if you use the -d option, it checks out the entire
repository the first time you try to update a working copy containing
a subset of the tree. But if you don't use the -d option you don't
get _any_ new subdirectories unless you specifically ask for them, and
you may not know which they are.
It would be nice if Subversion did this better.