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

Re: Existing Repos layout change - how badly will this break stuff ?

From: Stefan Sperling <stsp_at_elego.de>
Date: 2007-12-18 12:21:49 CET

On Tue, Dec 18, 2007 at 10:58:46PM +1300, Richard Shea wrote:
> I want to change my repository layout but before I do I'd like some
> advice on how/whether it will break things ...
>
> I have a repos like this ..
>
> /trunk
> /trunk/foo.c
> /trunk/bar.c
> /branches
> /tags
>
> ... and I want to change it to this ...
>
> /trunk
> /trunk/appname/
> /trunk/appname/foo.c
> /trunk/appname/bar.c
> /trunk/appdb/
> /trunk/appdb/insert.sql
> /trunk/appdb/delete.sql
> /branches
> /tags
>
> ... If I were to make that change and in the future I go looking at
> changes made to foo.c is the repos layout change described going to
> 'break' the chain at the point the layout change was made ?

Subversion will follow the path change backwards through
history unless you specify --stop-on-copy.

Tracing path changes forward through history (i.e. from lower to
higher revision numbers) is AFAIK not possible. This is likely
irrelavent to your use case though.
(And maybe this will change in 1.5, I vaguely remember cmpilato telling
me this was going to change in 1.5, but I might be mistaken.)

Play with a test repository and you'll see.

-- 
Stefan Sperling <stsp@elego.de>                 Software Developer
elego Software Solutions GmbH                            HRB 77719
Gustav-Meyer-Allee 25, Gebaeude 12        Tel:  +49 30 23 45 86 96 
13355 Berlin                              Fax:  +49 30 23 45 86 95
http://www.elego.de                 Geschaeftsfuehrer: Olaf Wagner

  • application/pgp-signature attachment: stored
Received on Tue Dec 18 12:22:13 2007

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

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