rooneg@gmail.com wrote on 08/01/2006 12:37:26 PM:
> On 8/1/06, Miha Vitorovic <mvitorovic@nil.si> wrote:
>
> > If I may... in most cases where you would be "delaying" the problem,
the
> > "out-of-date" error is somewhat confusing to the inexperienced users,
> > while in the complex cases the users would not be surprised to see it.
IMO
> > it would make the transition much smoother for the "why do I get
errors in
> > Subversion, but I didn't get them in <insert your VCS of choice>"
users.
>
> Honestly, I think you're wrong. I think it'll still be confusing in
> either case. This is a fundamental issue that comes when you start
> versioning directories and allowing mixed revision working copies, and
> if we can't fix it then we shouldn't try half-assed methods of hiding
> it that break down as soon as the user does practically anything of
> interest.
So are you saying that you do not think it is worth discussing whether
something, perhaps not "half-assed", could be done to improve this? Part
of my original post was that very question. I do not want to waste time
pursuing something that has no chance of going anywhere.
I do not disagree with you that eventually a user is going to run into
this and therefore should try to understand it, but I am still not
convinced that this could not work better. I think it is pretty hard to
explain/justify to a user that knows they are the only one that has done
anything on a given project or folder, that their local folder is "out of
date".
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 1 18:48:30 2006