>
>> -Original Message-
>> From: Michael McCandless [mailto:luc...@mikemccandless.com]
>> Sent: Friday, October 23, 2009 10:19 PM
>> To: java-dev@lucene.apache.org
>> Subject: Re: svn:mergeinfo prop
>>
>> OK thanks for the pointer :) It's very stran
e.apache.org
> Subject: Re: svn:mergeinfo prop
>
> OK thanks for the pointer :) It's very strange indeed.
>
> Mike
>
> On Fri, Oct 23, 2009 at 2:12 PM, Earwin Burrfoot wrote:
> > It's okay in a sense.
> > See, svn's merge-tracking support was gr
OK thanks for the pointer :) It's very strange indeed.
Mike
On Fri, Oct 23, 2009 at 2:12 PM, Earwin Burrfoot wrote:
> It's okay in a sense.
> See, svn's merge-tracking support was grafted onto it in a particulary
> hideous way and is really hairy on the insides.
> So while there's no sane expla
It's okay in a sense.
See, svn's merge-tracking support was grafted onto it in a particulary
hideous way and is really hairy on the insides.
So while there's no sane explanation for that behaviour, it is expected.
See -
http://svnbook.red-bean.com/en/1.5/svn.branchmerge.advanced.html#svn.branchme
I've noticed recently when merging from 2.9.x -> trunk or vice/versa,
for some reason it picks up files that had zero source changes in the
revision I merged, but do show changes to their svn:mergeinfo.
EG for LUCENE-2002, I merged 2.9.x -> trunk, and now on my trunk
checkout I see this mods:
Pro
