> It would be interesting to see if you can reproduce the
> problem in your environment with the 1.7.0-alpha1 release.
Hi Stefan... I will certainly give that a try.
> If you can reproduce it with 1.7, and have the time, could
> you try to come up with a reproduction recipe that produces
I
On Thu, Jun 09, 2011 at 02:51:47PM +0100, Echlin, Jamie wrote:
> > Hmmm...
> > Does the parent of the offending directory have
> > non-inheritable mergeinfo?
> > (Mergeinfo entries that have an asterisk appended are not
> > inheritable.)
>
> Hi Stefan...
>
> Before the merge only the source (/t
> Hmmm...
> Does the parent of the offending directory have
> non-inheritable mergeinfo?
> (Mergeinfo entries that have an asterisk appended are not
> inheritable.)
Hi Stefan...
Before the merge only the source (/trunk) and target
(branches/topic-XYZ) have mergeinfo, not parents or sub-director
On Thu, Jun 09, 2011 at 01:42:33PM +0100, Echlin, Jamie wrote:
> Hi Johan,
>
> > This is normal behavior of svn currently. Every subtree that
> > already has "explicit mergeinfo" (meaning it has its own svn:mergeinfo
> > property) will have that mergeinfo updated on every subsequent merge.
> > Th
Hi Johan,
> This is normal behavior of svn currently. Every subtree that
> already has "explicit mergeinfo" (meaning it has its own svn:mergeinfo
> property) will have that mergeinfo updated on every subsequent merge.
> That is done because it needs to be kept up to date.
Thanks for your respons
On Thu, Jun 9, 2011 at 1:18 PM, Echlin, Jamie
wrote:
> Further information on this... it's definitely not related to the authz
> as the same behaviour happens when using the file: protocol. It appears
> to be to do with the mergeinfo that's already present, as if I delete it
> all then it works as
Further information on this... it's definitely not related to the authz
as the same behaviour happens when using the file: protocol. It appears
to be to do with the mergeinfo that's already present, as if I delete it
all then it works as expected.
When doing a merge, is the mergeinfo anywhere othe
Morning,
Recently, when any user merges up from trunk to their topic branch, svn
appears to do it directory by directory for immediate sub-directories of
the branch root, so each sub-directory gets explicit mergeinfo.
[X:\XYZ.11650]svn merge http://svn.example.net/ABCD/Source/trunk
--- Merging r