You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Daniel Shahaf <da...@apache.org> on 2013/05/27 06:35:35 UTC
Re: svn commit: r1486500 - in /subversion/trunk/tools/server-side/svnpubsub: commit-hook.py revprop-change-hook.py svnpubsub/util.py svnwcsub.py
On Mon, May 27, 2013 at 02:52:10AM -0000, brane@apache.org wrote:
> Author: brane
> Date: Mon May 27 02:52:10 2013
> New Revision: 1486500
>
> URL: http://svn.apache.org/r1486500
> Log:
> In SvnPubSub, extract wrapper for subprocess.check_output into a common utility
> module. And make problems in the server hooks more visible by exiting with an
> error if the hook fails to run.
>
Should the exit code fix be backported?
Re: svn commit: r1486500 - in /subversion/trunk/tools/server-side/svnpubsub:
commit-hook.py revprop-change-hook.py svnpubsub/util.py svnwcsub.py
Posted by Branko Čibej <br...@wandisco.com>.
On 27.05.2013 06:35, Daniel Shahaf wrote:
> On Mon, May 27, 2013 at 02:52:10AM -0000, brane@apache.org wrote:
>> Author: brane
>> Date: Mon May 27 02:52:10 2013
>> New Revision: 1486500
>>
>> URL: http://svn.apache.org/r1486500
>> Log:
>> In SvnPubSub, extract wrapper for subprocess.check_output into a common utility
>> module. And make problems in the server hooks more visible by exiting with an
>> error if the hook fails to run.
>>
> Should the exit code fix be backported?
IMO, we can backport the whole set of changes in 1.8.1.
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com