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?
Joe
---------------------------------------------------------------------
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:06:14 2006