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

Re: update output idea

From: Mark <cm_mark_at_yahoo.com>
Date: 2002-04-27 04:48:25 CEST

--- Peter Davis <peter@pdavis.cx> wrote:
> On Friday 26 April 2002 06:16, Alexis Huxley wrote:
> > > % svn update
> > > Updated to revision 1788.
> > > %

> % svn update
> A ./foo
> M ./bar.txt
> Updated to revision 1788
> %

I think this might be confusing to users. What is the user hasn't updated for
12 commits, and the user is only updating a portion of the workarea that he/she
is working on. So, if the last time that foo was updated was commit 1781 and
bar.txt last commit was commit 1779, what does the notice of the lasted commit
revision of 1788 tell the user the files wher updated to that revision.

I don't know what the user can do with that info, a 'svn log -r1788 foo
bar.txt' may likely not return anything if they where not involved in commit

I don't know, I guess most on the list thought it was a good idea, I must be
missing something. I am still trying to get used to a "svn st -vn" on a file
telling me the the repository revision is 1796 but the file in my workarea is
1741, but it is up-to-date.


Do You Yahoo!?
Yahoo! Health - your guide to health and wellness

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 27 04:49:19 2002

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.