Jack Repenning <mailto:jrepenning@collab.net> wrote on 14 October 2004
01:28:
> On Oct 13, 2004, at 6:19 AM, C. Michael Pilato wrote:
>
>> Justin Erenkrantz <justin@erenkrantz.com> writes:
>>
>>> On Wed, Oct 13, 2004 at 10:06:27AM +0100, Ben Sewell wrote:
>>>> Just to add a potential comment from the Windows crowd; not preserving
>>>> extensions breaks the windows auto-launching behaviour for documents.
In my
>>>> situation, locked files are liable to be MS Excel files, for example;
if a
>>>> non-techie attempts a check-in, and it fails, and none of the
>>>> remaining
>>>
>>> Subversion already renames the extension when there is a merge
>>> conflict to '.mine', '.rXXXX', and '.rYYYY' I view the case of a
>>> lock race (?) to be essentially the same as a merge conflict from a
>>> user's perspective. -- justin
>>
>> And so the natural response is, perhaps we could fix this problem in
>> all cases, lock and merges alike. Any sane person can see the utility
>> in preserving the one piece of data that an entire operating system
>> uses to determine file types.
>
> More than one operating system.
>
So as not to break the current behaviour for merge conflicts, could this
behaviour be an option until v2.0? Perhaps as a "--preserve-extensions"
option on relevant commands, or a client-side WC option (do these exist?!
I'm new to svn, catching up as I can; currently using CVS; I'd put this in
the option in the equivalent of .cvsrc file, if there is one).
Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 14 13:18:19 2004