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

Re: Mergeinfo for skipped paths? (was: Re: Tree Conflicts and User Interface)

From: Danil Shopyrin <danil.shopyrin_at_gmail.com>
Date: Mon, 22 Sep 2008 22:32:42 +0400

> Write access to some siblings of skipped path can be restricted. In that case:
> A) user will be disappointed because commit will be prohibited;
> B) inconsistent mergeinfo will be committed even if user will manually
> remove mergeinfo on write-restricted paths.
> Write-restriction rarely occurs in the open-source development but
> it's a common practice in "the industry". And write-restricted users
> are usually not-a-very-experienced programmers. And they can be not
> very familiar with advanced Subversion topics.

It's fair to say that this problem can be avoided if we will not write
mergeinfo for unaffected paths. Am I understand properly, that we are
not requested to write explicit mergeinfo to unaffected siblings of
the skipped paths in that case?

E.g. if not-writing-explicit-mergeinfo-for-unaffected-paths discussed
at http://svn.haxx.se/dev/archive-2008-09/0443.shtml will be
implemented, can we get the following mergeinfo with your approach?

Properties on 'branch':
   /trunk:2,4* <--- Non-inheritable mergeinfo.
Properties on 'branch/bar.c':
Properties on 'branch/subdir':
   <null> <-- subdir isn't somehow affected by the merge.

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-23 00:02:34 CEST

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.