Re: Forcing svn:eol-style=native on files with "binary" mime types?

Philip Martin wrote:
> Aleksey Nogin <aleksey@nogin.org> writes:
>
>>Then why doesn't it allow setting snv:eol-style=native on a file with
>>an application/x-foo mime type?
>
> Because it's usually a mistake.

That's fine as a reason why it behaves that way currently, but (without having
checked the details) I think it's wrong and should be allowed at least with
"--force".

>>Is there a way _at all_ to tell
>>subversion "this is a file with _unmergeable_ data and _native_ eol
>>style"?

[Via auto-props.] Apparently not. I think it would be right to modify the
auto-props handling so that this combination is allowed. After all, auto-props
is a configuration which the user has the opportunity to test, not a
command-line option that is immediately acted upon, so it is not appropriate to
disallow the combination just because it is usually a mistake.

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 22 19:22:45 2005