[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Explanation on the conflict and "svn resolve" functionnality

From: Jason E. Stewart <jason_at_openinformatics.com>
Date: 2004-04-07 10:47:03 CEST

Ben Collins-Sussman <sussman@collab.net> writes:

> The question is: is the inconsistency an annoying problem, or is it an
> extra bit of user-friendliness? I can see somebody arguing either way.
> However, hundreds (thousands?) of people have been using Subversion for
> 2 years or so now, and this is the first time I've ever heard anyone
> complain about this inconsistency. So based on experience, I'm
> *guessing* that the status quo is the better choice.

Perhaps the real issue is that 'svn status' is not properly listing
the two conflict files as being under svn control. cleanAll is using
'svn status to determine which files are under SVN control, and they
are not listed, so most users would assume what Alexis assumed.

Perhaps a flag can be added to status that shows import SVN admin
files, like the conflict files (I don't know if there are any other
files like this).

That would solve the problem with cleanAll, and make users like myself
understand the issue better.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 8 17:56:07 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.