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

Re: merge tracking and revision number fragility

From: Travis P <svn_at_castle.fastmail.fm>
Date: 2004-10-07 18:19:24 CEST

On Oct 7, 2004, at 10:55 AM, Guido Anzuoni wrote:
> Just a warning about the use of this technique.
>
> If the repository is dumped and not fully reloaded (starting at some
> revision) or
> is loaded into an existing repository with --parent-dir switch, then
> the comment
> will refer rev. numbers that were valid in the previous repository but
> the
> actual "playedback" transactions have gengerate different revision
> numbers.

Yes, though I do record merges as the book suggests, the problem that
Guido notes has crossed my mind more than once.

It imposes a requirement that all decisions about what projects need to
live in which repositories needs to be made correctly
the first time because change later will cause big headaches with
revision numbers in log messages or elsewhere no longer matching.

Example: You have two small server machines serving two repositories,
but then a big new server is bought and you want to combine the
repositories for various benefits: can 'svn mv/cp' code between
projects that used to be impossible because they lived on separate
repos, can reduce backup and similar administrative overhead because
just one repos is less work than two. Unfortunately, any combination
will necessarily cause revnumbers in at least one repository to become
invalid. I'm sure there are a hundred other examples.

Subversion is still new, so I don't think that this problem is being
encountered today as it will be in the future and large repos are
merged/separated as hardware changes, management/team/company
organizational relationships change, geography changes. I can imagine
all kinds of scenarios causing future pain related to this.

This type of "you have to make the decision correctly the first time
because change later will cause big headaches" problem is like to that
of CVS directory structure which many of us (certainly including
Subversion developers) dislike intensely.

-Travis Pouarz

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 7 18:19:49 2004

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.