Johan Corveleyn wrote:
> On Wed, Apr 28, 2010 at 11:58 PM, Neels J Hofmeyr wrote:
> [...]
>> We use that in a hook script that forbids
>> commits that replace nodes -- because some users often do that by accident,
>> fragmenting history --
>
> Probably because of this bug?
> http://subversion.tig
On Wed, Apr 28, 2010 at 11:58 PM, Neels J Hofmeyr wrote:
[...]
> We use that in a hook script that forbids
> commits that replace nodes -- because some users often do that by accident,
> fragmenting history --
Probably because of this bug?
http://subversion.tigris.org/issues/show_bug.cgi?id=3429
Bolstridge, Andrew wrote:
>> -Original Message-
>> From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
>> Sent: Mon 26/04/2010 19:27
>> To: Bolstridge, Andrew
>> Cc: dev@subversion.apache.org
>> Subject: RE: Feature idea: user-configurable post-c
>-Original Message-
>From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
>Sent: Mon 26/04/2010 19:27
>To: Bolstridge, Andrew
>Cc: dev@subversion.apache.org
>Subject: RE: Feature idea: user-configurable post-commit notifications
>
>Bolstridge, Andrew wrote on F
Bolstridge, Andrew wrote on Fri, 23 Apr 2010 at 13:52 +0100:
> So imagine if I (as a server admin, of course) could configure a new
> command ("svn review" or "svn special-cmd review") that uses the
> same mechanism as pre-commit, and calls the server hook
> "special-review.
On 23.04.2010 00:06, Hyrum K. Wright wrote:
> With the increased integration of build tools and other notification
> systems which desire knowledge of commit activity, it would be useful
> to provide an easier mechanism of installing post-commit notification,
> without having to use the hook inf
Greg Stein wrote on Fri, 23 Apr 2010 at 07:17 -0400:
> And I'll go one further: also provide a (sample) CGI script to
> *accept* those POST requests, and "do something". At the ASF, our
> website is updated after a commit. The code that does that today is
> apparently a little flaky, so having an o
On Fri, Apr 23, 2010 at 07:07, Stefan Küng wrote:
>...
>>> On 23.04.2010 00:06, Hyrum K. Wright wrote:
With the increased integration of build tools and other notification
systems
which desire knowledge of commit activity, it would be useful to provide
an
easier mecha
On 23.04.2010 13:00, Greg Stein wrote:
On Fri, Apr 23, 2010 at 06:53, Stefan Küng wrote:
On 23.04.2010 00:06, Hyrum K. Wright wrote:
With the increased integration of build tools and other notification
systems
which desire knowledge of commit activity, it would be useful to provide
an
easier
On Fri, Apr 23, 2010 at 06:53, Stefan Küng wrote:
> On 23.04.2010 00:06, Hyrum K. Wright wrote:
>>
>> With the increased integration of build tools and other notification
>> systems
>> which desire knowledge of commit activity, it would be useful to provide
>> an
>> easier mechanism of installing
On 23.04.2010 00:06, Hyrum K. Wright wrote:
With the increased integration of build tools and other notification systems
which desire knowledge of commit activity, it would be useful to provide an
easier mechanism of installing post-commit notification, without having to
use the hook infrastructu
On 23.04.2010 11:45, Bert Huijben wrote:
>> -Original Message-
>> From: Greg Stein [mailto:gst...@gmail.com]
>> Sent: vrijdag 23 april 2010 0:57
>> To: Hyrum K. Wright
>> Cc: Subversion Development
>> Subject: Re: Feature idea: user-configurable post-com
> -Original Message-
> From: Greg Stein [mailto:gst...@gmail.com]
> Sent: vrijdag 23 april 2010 0:57
> To: Hyrum K. Wright
> Cc: Subversion Development
> Subject: Re: Feature idea: user-configurable post-commit notifications
>
> Write a hook script to do exactly t
Write a hook script to do exactly that, and make it part of the
standard release.
In some future release, after that script and its features stabilize,
*then* we can consider placing into into the core code.
I fear the security aspects of something like you talk about: anybody
with commit access
14 matches
Mail list logo
