On Dec 24, 2004, at 3:02 AM, Benjamin Pflugmann wrote:
> On Wed 2004-12-22 at 15:13:24 -0800, you wrote
>> On Tue, 21 Dec 2004 08:27:18 -0600, Ben Collins-Sussman wrote:
>>> This is our way of preventing users from editing unmergeable files
>>> without locking first (and possibly discovering existing locks,
>>> thus preventing time wastes.) The theory is that users/admins
>>> would only set this new property on unmergeable files. But if you
>>> want to set it on everything, that would work too, I guess. You'd
>>> have a 100% read-only working copy.
>>
>> In 1.2, will we be able to configure the server to automatically set
>> this property for any file that is detected as binary?
>
> In Subversion's design, the server may not change any properties
> without an explicit commit (because working copyies which think they
> are up to date would break).
>
> But you can easily install a pre-commit hook that is rejecting any
> commit where not all binary files have that property set. Not the
> perfect solution, but good enough.
Is it the client or the server that decides if a file is binary or not?
It would be nice if the client-side auto-props could be made to set
this. Instead of using a filename pattern, if there was a way to
specify binary or not in the pattern matching that would be cool.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Dec 25 23:38:27 2004