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

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

-- 
Danil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org