On Thu, 14 Oct 2004, Garrett Rooney wrote:
> C. Michael Pilato wrote:
>
> > That's a good idea, but then we'd have to maintain support for the new
> > --preserve-extensions flag after 2.0 (as a no-op). I don't believe we
> > are obligated to maintain the existing naming structure of this files.
> > Humans and scripts aren't supposed to be looking for conflict files
> > based on their knowledge of our naming scheme -- they should be
> > parsing the output of 'svn info' to see the names of any conflict
> > files.
>
> Umm, that seems a little unreasonable, since the format of those
> filenames is documented in numerous places, including both your book and
> mine ;-)
>
> I'm almost certain that someone is depending on that right now, and
> changing it out from under them seems like a bad idea.
>
Is it also documented that, if foo is conflicted and foo.mine (etc.)
already exists, then foo.2.mine will be created. People just depending on
foo.mine are already broken.
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 14 21:59:40 2004