Re: svn commit: r1817713 - in /subversion/site/staging/docs/release-notes: 1.6.html 1.6.zh.html

On 10/12/2017 15:06, luke1410_at_apache.org wrote:
> Author: luke1410
> Date: Sun Dec 10 14:06:19 2017
> New Revision: 1817713
>
> URL: http://svn.apache.org/viewvc?rev=1817713&view=rev
> Log:
> Replace no longer working collabnet viewcvs link to pre-lock stdout lock-token
> support commit with corresponding svn.apache.org one.
>
> site/staging/release-notes/1.6.html,
> site/staging/docs/release-notes/1.6.zh.html: update link
>
> Modified:
> subversion/site/staging/docs/release-notes/1.6.html
> subversion/site/staging/docs/release-notes/1.6.zh.html
>
> Modified: subversion/site/staging/docs/release-notes/1.6.html
> URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.6.html?rev=1817713&r1=1817712&r2=1817713&view=diff
> ==============================================================================
> --- subversion/site/staging/docs/release-notes/1.6.html (original)
> +++ subversion/site/staging/docs/release-notes/1.6.html Sun Dec 10 14:06:19 2017
> @@ -891,7 +891,7 @@ without this option:
>
> <p>The <tt>pre-lock</tt> hook can now specify the lock-token string
> via the hook's stdout; see <a
> -href="http://svn.collab.net/viewcvs/svn?rev=32778&amp;view=rev"
> +href="https://svn.apache.org/viewvc?view=revision&revision=872852"
> >r32778</a> for details. Note that when the hook uses this feature,
> it must take responsibility for ensuring that lock tokens are unique
> across the repository.</p>
>
> Modified: subversion/site/staging/docs/release-notes/1.6.zh.html
> URL: http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.6.zh.html?rev=1817713&r1=1817712&r2=1817713&view=diff
> ==============================================================================
> --- subversion/site/staging/docs/release-notes/1.6.zh.html (original)
> +++ subversion/site/staging/docs/release-notes/1.6.zh.html Sun Dec 10 14:06:19 2017
> @@ -698,7 +698,7 @@ href="https://svn.apache.org/repos/asf/s
> </h3>
>
> <p><tt>pre-lock</tt>钩子现在可以通过标准输出指明锁定令牌字符串；详细请看<a
> -href="http://svn.collab.net/viewcvs/svn?rev=32778&amp;view=rev"
> +href="https://svn.apache.org/viewvc?view=revision&revision=872852"
> >r32778</a>。注意，当钩子用了这个特性，必须确保锁定令牌在版本库范围是唯一的。</p>
>
> <p>Subversion 1.6有许多新的修正的API需要列出来，一般的API信息可以看<a
>
>
I tried to dig up the corresponding commit from the old collabnet repo
(revision 32778) to the corresponding one in the a.o repo.

r872853 contains the following log message: "Follow up to r32778 with
the appropriate notes for the future 1.6 release."

From that one, the fact that that both commits are from the same
contributor (kfogel), and the corresponding log message matching the
content from the 1.6-release notes page, I conclude that the
corresponding previous commit (r872853) is the one which previously was
referred to as r32778 in the collabnet repository:
https://svn.apache.org/viewvc?view=revision&revision=872852

I'd still appreciate, if someone who happens to slightly remember which
revision this release notes was linked against, could verify that the
replacement link is correct (see:
http://subversion-staging.apache.org/docs/release-notes/1.6.html ).

Regards,
Stefan
Received on 2017-12-10 15:15:54 CET