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

RE: RE: Communication of LOCKS and CHANGES

From: Harvey, Edward <Edward.Harvey_at_patni.com>
Date: 2007-11-21 16:14:35 CET

> From: Brian Erickson [mailto:erickson@BAUERCONTROLS.com]
> 1) pcs42xx D:\junk>svn status
> M trunk\test.txt
> 2) pcs42xx D:\junk>svn status -u
> M * 63 trunk\test.txt
> Status against revision: 64
> 3) pcs42xx D:\junk>svn status
> M trunk\test.txt
> be a large change (I'm guessing) to the code. However, and more
> importantly, it's a large change to the meaning of the status command.

This is a very good point, and I'm inclined to agree. If a new feature
were implemented for caching of previously retrieved information about
the repository, it must not change the existing behavior of existing

If something new were created, I think it would really have to be
something new. If it creates a new line for some files like
"repository-rev" in the entries file, then the new line could safely be
ignored by existing commands such as "svn status"

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

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.