On Fri 2004-12-24 at 09:28:54 -0500, Scott Palmer wrote:
> On Dec 24, 2004, at 3:02 AM, Benjamin Pflugmann wrote:
> > >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's the client. The client does all eol and keyword translation, and
it's also only the client that knows the concept of line-oriented diffs.
The server knows nothing about all this, and handles everything the
The decision whether a file is considered binary or not is based on
it's svn:mime-type property, see
describes when svn:mime-type is set and how you can influence
automatically setting it.
> It would be nice if the client-side auto-props could be made to set
You can ...
> Instead of using a filename pattern,
... but only with file patterns.
> if there was a way to specify binary or not in the pattern matching
> that would be cool.
As the cited book section explains, the internal heuristic looks at
the content and should usually do the Right Thing.
But what you are missing to your luck is being able to set a property
based on the value of another property. But as was said before, you
can now easily reject commits having binary files without the
need-lock property. And writing a script for the client-side that
looks for all binary files and sets this property shouldn't be to hard
to do, either.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Dec 24 16:16:55 2004