RE: Communication of LOCKS and CHANGES

> I would hope that any GUI that retained this information would also
> display a time-stamp of when this temporary status snapshot was
> obtained
> to make it clear that it is not the current state.

If the file is "out of date" there's no need for a timestamp. Once the
file is out of date, it's permanently out of date until you do an
update.

If the file is "locked in the repository by some other user," then
there's also (most of the time) no need for a timestamp, because most of
the time the person who locked it will soon commit a change. But I
certainly have no objection to communicating the timestamp of when the
gui client discovered the remote repository lock. It'll hurt nothing to
know the timestamp, but I don't think it's awesomely necessary.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 21 18:39:00 2007