[Laszlo-dev] SVN complaint
jgrandy at openlaszlo.org
Tue Jun 13 01:00:34 EDT 2006
[Redirecting to Laszlo-dev]
An additional option would be to enforce svn:eol=native property on
all text files added or imported. This could be done using a pre-
commit hook. It would have the effect of requiring that every
committer have auto-props turned on.
(Note that automatically setting svn:eol=native in the pre-commit
hook is a bad idea, according to the svn book, since the committing
client is then out of sync with the database. Subversion apparently
doesn't recover well from this.)
On Jun 12, 2006, at 9:50 PM, Jim Grandy wrote:
> On Jun 12, 2006, at 6:13 PM, P T Withington wrote:
>> It seems to me that SVN does not handle line breaks correctly. In
>> p4 when I checked out files the line breaks were translated to my
>> platform line break. In svn I keep seeing files with DOS line
>> breaks in them. Surely that cant' be right?
> It works fine for me, but then I'm using a modern text editor that
> automatically detects a file's line break usage and adapts to suit :-)
> But since there are folks who don't have the luxury or the desire
> to use such an editor (another :-), Subversion offers a way out.
> Unfortunately, the solution isn't really centralized.
> Three things we can do:
> 1. manually go through the repo and apply the svn:eol=native
> property to every text file. This could be done with a script, I
> suppose. It would have the effect of transparently mapping to/from
> the repository to your native eol style. But what a PITA.
> 2. enable auto-props in your local ~/.subversion/config file (see
> svn book, chapter 7, Runtime Configuration Area) and add rules that
> automatically apply the svn:eol=native property to each text file
> that is added/imported into the repository. Each user should have
> this turned on. Unfortunately, it doesn't apply to co/ci, just add/
> 3. add a pre-commit hook that rejects any text file checked in with
> anything other than Unix eol style
> Realistically, if we are going to fix this, we'll need to do both 1
> and have everyone do 2. Number 3 isn't going to be popular, but
> neither is it necessary.
> By the way, the ~/.subversion/config file also has a way of
> filtering out build products from 'svn status'. See the config
> option 'global-ignores'.
> I've added notes about both of these things to http://
More information about the Laszlo-dev