On 11/12/2017 23:46, luke1...@apache.org wrote:
> Author: luke1410
> Date: Mon Dec 11 22:46:17 2017
> New Revision: 1817862
>
> URL: http://svn.apache.org/viewvc?rev=1817862=rev
> Log:
> * site/staging/docs/release-notes/1.4.html: Replace a dead link to the
> Berkeley DB upgrade guide.
>
>
On 11/12/2017 18:15, Daniel Shahaf wrote:
> julianf...@apache.org wrote on Mon, 11 Dec 2017 13:41 +:
>> Modified:
>> subversion/site/publish/docs/community-guide/releasing.part.html
> Could you backport this to staging/ so future changes to staging don't
> merge conflict when they are
Author: luke1410
Date: Mon Dec 11 22:46:17 2017
New Revision: 1817862
URL: http://svn.apache.org/viewvc?rev=1817862=rev
Log:
* site/staging/docs/release-notes/1.4.html: Replace a dead link to the
Berkeley DB upgrade guide.
Modified:
subversion/site/staging/docs/release-notes/1.4.html
Author: luke1410
Date: Mon Dec 11 22:38:54 2017
New Revision: 1817861
URL: http://svn.apache.org/viewvc?rev=1817861=rev
Log:
* site/publish: Merge from staging.
Modified:
subversion/site/publish/ (props changed)
subversion/site/publish/docs/release-notes/1.6.zh.html
Propchange:
Author: luke1410
Revision: 1817719
Modified property: svn:log
Modified: svn:log at Mon Dec 11 22:37:27 2017
--
--- svn:log (original)
+++ svn:log Mon Dec 11 22:37:27 2017
@@ -1,2 +1,2 @@
-- site/staging/docs/index.html:
Author: luke1410
Date: Mon Dec 11 22:34:09 2017
New Revision: 1817860
URL: http://svn.apache.org/viewvc?rev=1817860=rev
Log:
* site/staging: Catch-up merge from 'publish'
Modified:
subversion/site/staging/ (props changed)
subversion/site/staging/docs/community-guide/releasing.part.html
Author: danielsh
Date: Mon Dec 11 22:02:48 2017
New Revision: 1817856
URL: http://svn.apache.org/viewvc?rev=1817856=rev
Log:
Fix segfault when no home directory is available.
This can be reproduced by forcing svn_user_get_homedir() to return NULL.
However, I can't imagine a situation in which
Author: danielsh
Date: Mon Dec 11 21:37:34 2017
New Revision: 1817848
URL: http://svn.apache.org/viewvc?rev=1817848=rev
Log:
* publish/docs/community-guide/releasing.part.html
(release-branches): Correct the suggested commit message.
Modified:
Author: danielsh
Revision: 1817837
Modified property: svn:log
Modified: svn:log at Mon Dec 11 21:34:52 2017
--
--- svn:log (original)
+++ svn:log Mon Dec 11 21:34:52 2017
@@ -6,4 +6,4 @@ section for the upcoming 1.10.0
Author: julianfoad
Date: Mon Dec 11 21:18:29 2017
New Revision: 1817837
URL: http://svn.apache.org/viewvc?rev=1817837=rev
Log:
Increment the trunk version number, and introduce a new CHANGES
section for the upcoming 1.10.0 release.
*
Author: julianfoad
Date: Mon Dec 11 20:12:17 2017
New Revision: 1817816
URL: http://svn.apache.org/viewvc?rev=1817816=rev
Log:
* publish/docs/community-guide/releasing.part.html
(release-branches): Remove a step obsoleted by r1700215.
Modified:
Author: julianfoad
Date: Mon Dec 11 19:58:02 2017
New Revision: 1817814
URL: http://svn.apache.org/viewvc?rev=1817814=rev
Log:
* subversion/include/private/svn_element.h,
subversion/libsvn_delta/element.c
(svn_element__tree_set): Remove unused 'svn_error_t *' return.
Found by: danielsh
julianf...@apache.org wrote on Mon, 11 Dec 2017 13:41 +:
> Modified:
> subversion/site/publish/docs/community-guide/releasing.part.html
Could you backport this to staging/ so future changes to staging don't
merge conflict when they are published?
> +++
Author: julianfoad
Date: Mon Dec 11 13:41:35 2017
New Revision: 1817775
URL: http://svn.apache.org/viewvc?rev=1817775=rev
Log:
* publish/docs/community-guide/releasing.part.html
(release-branches): Add a step: 'ensure buildbots build the new branch'.
Suggested by: brane
Modified:
Author: julianfoad
Date: Mon Dec 11 13:22:31 2017
New Revision: 1817773
URL: http://svn.apache.org/viewvc?rev=1817773=rev
Log:
Create the 1.10.x release branch.
Added:
subversion/branches/1.10.x/ (props changed)
- copied from r1817772, subversion/trunk/
Propchange:
15 matches
Mail list logo