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

Re: [PATCH] new parameter option '--verbose' for 'svn update'

From: <Mathias.Weinert_at_gfa-net.de>
Date: 2005-09-29 17:35:10 CEST

"Max Bowsher" <maxb@ukf.net> wrote:

> Mathias.Weinert@gfa-net.de wrote:
> > Hi there,
> >
> > as I sometimes wanted to know what 'svn update' will do and which was the
> > current revision of my working copy I implemented a '--verbose' option for
> > 'svn update' which provides these information:
> >
> > $ svn up -v myWorkingCopy/
> > Current revision 409
> > will be updated to revision 413.
> > U    foo.c
> > A    bar.c
> > Updated to revision 413.
> >
> > The information is only shown when current revision is not the same as the
> > new revision.
> >
> > If you find this option usefull I would be happy if you added it to
> > subversion. If not, never mind.
> IIUC, this just shows the revision of the root directory of the update.

That's right.

> That would be misleading, and not very helpful, if your WC contains mixed
> revisions.

IMHO this is helpful.
First, If I regularly make updates of a WC 'svn up -v' will in most cases show the revision at which I made my last 'svn up' (until I make a commit on the root of my WC).
Second, we always have the "problem" with mixed revisions:
If I for example do an 'svn log' for a WC path I will only get the log until the revision I last committed or updated this part of the WC but not the whole log. For me this is much more misleading, or, to say it in other words, users have to know what this functions do and what they don't.

--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org For additional commands, e-mail: dev-help@subversion.tigris.org Received on Thu Sep 29 18:58:27 2005

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.