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

Re: Migrating repository from Windows to UNIX and eol-style

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-07-03 18:19:17 CEST

On Jul 3, 2006, at 18:05, Joe wrote:

> Erik Huelsmann wrote:
>> Right. We learned from CVS in this respect: many a time people forgot
>> to use the 'this is a binary file, please don't modify'-option when
>> adding an image to the repository. Most of them were damaged,
>> sometimes not even recoverable (because the original was deleted).
> OK, that's the strongest argument for doing it the Subversion way
> (and I won't press the issue further).
>> Absolutely. This is one of Subversion's weak spots. You as a sysadmin
>> can prevent the file ending up in the repository by checking for the
>> right properties and rejecting the 'newbie commit' in a post-commit
>> hook.
>> [snip] If you have resources to spare (time to discuss design or
>> implementation), you're most welcome to come to dev@ and stirr up the
>> discussion again. You can read about it all through the mailing list
>> archives at http://svn.haxx.se/dev/
> I don't have much time to spare, but I'm thinking that one thing
> that would help sysadmins is some way of storing default properties
> at the server, e.g., allowing a project to specify something like
> "from this tree node down, all .c/.h files are defaulted to text
> and svn:eol-style native, and all .jpg/.png files default to the
> respective image mime-types". Of course, one can implement this by
> storing a config file (or config template) at that point in the SVN
> tree (or some parallel tree) and require developers to fetch it and
> adapt it as their first order of business, but a Subversion-
> provided facility would be preferable. What is the rationale for
> not storing default props at the server?

I'm not sure what the rationale is, other than maybe it hasn't been
high enough on anyone's priority list to work out exactly how such a
feature should be implemented. But it's certainly possible to write a
pre-commit hook that implements that behavior. If I ever get around
to writing my web-based Subversion administration toolkit, that would
be one of the scripts I'd provide.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 3 18:20:46 2006

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.