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

RE: Fixing time stamps

From: Sander Striker <striker_at_apache.org>
Date: 2003-10-30 14:26:47 CET

> From: Philip Martin [mailto:philip@codematters.co.uk]
> Sent: Thursday, October 30, 2003 2:19 PM

> "Sander Striker" <striker@apache.org> writes:
> > So when do we find out? Would we know during an svn status run?
> > During svn update? Does this require a write lock to detect?
> Subversion detect's it every time status (or revert or commit) is run.

Ok, I can see us repairing automagically at revert and commit then.
What about status? If it detects a bogus timestamp, can it at that
point take out a write lock and attempt to repair?

> There is no way, at present, for the user to find out that Subversion
> has detected the problem.

Failing the above, would an extra notice in the status output help?
'T' for bogus timestamp? This would then prompt the user to run
svn cleanup (while not requiring it). Ofcourse this could be unclear...
and given the new status output, potentially overkill.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 30 14:27:39 2003

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

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