Re: svn commit: r1746281 - /subversion/branches/1.9.x/README

[Evgeny Kotkov <ev...@visualsvn.com>]

Stefan Hett <lu...@apache.org> writes:

> New Revision: 1746281
>
> URL: http://svn.apache.org/viewvc?rev=1746281&view=rev
> Log:
> * README
>   Correct the svnbook sources URL (now hosted on SourceForge).
>
> Obvious fix.
>
> Patch by: Pavel Lyalyakin <pa...@visualsvn.com>
>
> Modified:
>     subversion/branches/1.9.x/README

This commit doesn't look like a backport — there's no svn:mergeinfo
and the log message doesn't say which revision was merged.

Could you please reapply this change by merging r1746277 from trunk?

This way, the change will show up properly in `svn log -g', and doing so
is also going to avoid conflicts in case something else is changed and
backported in this part of the file.


Thanks,
Evgeny Kotkov

Re: svn commit: r1746281 - /subversion/branches/1.9.x/README

[Stefan Hett <st...@egosoft.com>]

On 5/31/2016 5:37 PM, Evgeny Kotkov wrote:
> Stefan Hett <lu...@apache.org> writes:
>
>> New Revision: 1746281
>>
>> URL: http://svn.apache.org/viewvc?rev=1746281&view=rev
>> Log:
>> * README
>>    Correct the svnbook sources URL (now hosted on SourceForge).
>>
>> Obvious fix.
>>
>> Patch by: Pavel Lyalyakin <pa...@visualsvn.com>
>>
>> Modified:
>>      subversion/branches/1.9.x/README
> This commit doesn't look like a backport \u2014 there's no svn:mergeinfo
> and the log message doesn't say which revision was merged.
>
> Could you please reapply this change by merging r1746277 from trunk?
>
> This way, the change will show up properly in `svn log -g', and doing so
> is also going to avoid conflicts in case something else is changed and
> backported in this part of the file.
Ouch. Thanks for spotting that Evgeny. Corrected in r1746296 (same 
correction also done in the 1.8 backport).

FWIW: The problem was me using the wrong protocol in the URL (http 
instead of https). http URL removed from the cache now, so it shouldn't 
happen again.

-- 
Regards,
Stefan Hett