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

RE: any "must-have" hooks to implement on svn server?

From: <christian.peper_at_kpn.com>
Date: Thu, 24 Jul 2008 15:38:03 +0200

Thanks everyone so far for your great answers! It really helps. :)

> -----Original Message-----
> From: David Weintraub [mailto:qazwart_at_gmail.com]
> Sent: Wednesday, July 16, 2008 9:58 PM
> Subject: Re: any "must-have" hooks to implement on svn server?
> [...]
> Another hook I have is one that verifies that particular
> subversion properties are attached to your files before being
> committed. For example, we want all files that end in *.sh,
> *.pl, and *.makefile to have the property "svn:eol-style" =
> "LF". Users can configure auto-properties, but this
> guarantees that the property is on the file before being
> committed.


what I don't understand is why, if svn:eol-style=native always chooses
the correct format for the destination system, why the other specific
options even exist. Except for backward compatibility of course.
Why not write a pre-commit hook that checks if the file type is some
text file, aka not binary, and set the eol-style to native and be done
with it? No bothering users with client=side config that they forget to
update, save, maintain or even apply at all. You also don't need to
maintain the hooks when new file types get added that you haven't
supported yet.


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-24 18:04:56 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.