RE: Mergeinfo overwritten from successive merges
From: Bert Huijben <bert_at_qqmail.nl>
Date: Fri, 14 Mar 2014 14:20:49 +0100
The base revision for out of date checks could be different per node... (E.g. Mixed revision working copies). At which revision we open the transaction shouldn't really matter if we check the revision for the individual nodes.
For content changes we supply the baseline rev for v2 via an header... And my guess would be that we forgot to do that for the proppatch.(v1 supplied base URL). Most tests in our test suite would check for out of date via the root of the commit editor... So that would explain things.
But that is 100% without looking at the code...
Philip Martin <philip.martin_at_wandisco.com> writes:
> Bert Huijben <bert_at_qqmail.nl> writes:
It seems to me that mod_dav_svn should not be solely responsible here.
I'm a bit surprised that we chose to have mod_dav_svn create
-- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*Received on 2014-03-14 14:23:17 CET
This is an archived mail posted to the Subversion Dev mailing list.