[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: Scott Palmer <scott.palmer_at_2connected.org>
Date: 2004-10-07 20:20:07 CEST

On Oct 7, 2004, at 1:38 PM, Simon Large wrote:

> "Guido Anzuoni" wrote
>>> [Thrown out to the group at large]
>>> So, do all svn users follow the book convention of
>>> using a comment to indicate that a "merge occurred
>>> with these source/destination revisions" ? Are there
>>> any other techniques for tracking this that other
>>> developers/Conf Mgrs use?
>
>> 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.
>
> This is one instance where the concept of a 'label'
> which marks a prticular sub-tree at a particular revision
> would actually be useful, provided that a dump/load cycle
> updates it to the correct position. Maybe merge tracking
> and labels are related and could be introduced together.

I think the cheap-copy 'tag' still works for this.

Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 7 20:20:29 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.