Re: Conflict file naming

"Michael Pilato" <cmpilato@collab.net> writes:
> Bah. We've always had entries-file data and 'svn info' output to
> accurately reveal the correct names of conflict files, if any. If folks
> are careless enough to write scripts that completely ignore easily
> query-able sources of canonical information like that in favor of whack
> guesses based on file naming schemes, I've no sympathy for them.

No, the issue isn't discovering the name -- that part's easy. The
issue is that when you load these files into editors (or other
programs) that use file-extension as a way of determining file type,
then all of a sudden things don't work right.

File extensions have been a semi-standardized source of information
for many, many years. I feel like it's Subversion that's misbehaving
here: when we add our own extension, we're blowing away useful data.
If adding our own extension were our only choice, I'd say fine, let's
do it. But there's no need for it -- we could just as easily put the
Subversion-specific portion elsewhere in the filename.

-Karl

-- 
www.collab.net  <>  CollabNet  |  Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org