Re: Reducing "out-of-date" errors

rooneg@gmail.com wrote on 01.08.2006 16:56:57:

> On 8/1/06, Mark Phippard <markp@softlanding.com> wrote:
>
> > I do not know, that is why I asked. I think it would help, and it
goes a
> > little beyond this trivial use case. You could have done an
> > update/checkout so that you were at HEAD, then done a commit, now you
want
> > to do a rename or property set. If it so happened that there had not
been
> > other activity on your project, then that last commit would have kept
your
> > folders up to date and you could perform the operation without an
update.
>
> See, the problem here is that it's making the problem rarer, but not
> making it go away entirely, so all you're doing is delaying the user
> running into it, which means when they do hit it they're less likely
> to know what's wrong.

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.

Best regards,

---
  Miha Vitorovic
  Inženir v tehničnem področju
  Customer Support Engineer
   NIL Data Communications,  Tivolska cesta 48,  1000 Ljubljana,  Slovenia
   Phone +386 1 4746 500      Fax +386 1 4746 501     http://www.NIL.si
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org