[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn:eol-style and other text transforms on commit

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2007-10-23 19:49:31 CEST

On 10/23/07, Kenneth Porter <shiva@sewingwitch.com> wrote:
> On Tuesday, October 23, 2007 2:16 PM +0200 Erik Huelsmann
> <ehuels@gmail.com> wrote:
> > (Server regulated) hooks on the client, built into subversion, would
> > (a) open gaping security holes and (b) significantly raise the
> > dependencies requirements (which scripting environment? Python? On
> > Windows it's not 'the default'...)
> How about the client supplying the hook (an arbitrary executable)
> optionally? The server then runs its pre-commit hook as usual to verify
> that the client's hook has run. For example, the client could run an
> arbitrary formatting program and then the server checks that the result
> meets the formatting standards and rejects if it doesn't.

Wouldn't that still have security implications?

Why not just make the developer responsible for doing this himself
(still reject the commit via hook if it doesn't pass tests)?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 23 19:49:56 2007

This is an archived mail posted to the Subversion Users mailing list.