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

Re: rapidsvn feedback

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-07-30 06:04:37 CEST

"Peter Johnson" <peterj@nec.com.au> writes:

> > -----Original Message-----
> > From: Branko ?ibej [mailto:brane@xbc.nu]
> > Sent: Tuesday, July 30, 2002 12:51 PM
> > To: Peter Johnson
> > Cc: dev@subversion.tigris.org
> > Subject: Re: rapidsvn feedback
> >
> > Peter Johnson wrote:
> >
> > >I'd like to see the UI terminology changed.
> > >For example, the following table may be used to translate the
> existing
> > >UI terminology into something more familiar.
> > >
> > >Update -> Get latest
> > >
> >
> > This would be less than true. You can update to something other than
> HEAD.
>
> In that case may be an interface is needed to select the revision or
> branch?

Yes. Every working copy represents some URL at some revision.

Teh 'svn update' makes your working copy identical to its current URL,
but in a different revision. 'svn switch' makes your working copy
represent any arbitrary (revision, URL) pair.

>
> > >Commit -> Check in
> > >Revert -> Check out
> > >
> >
> > Revert does not mean the same as check out. In fact it means something
> > quite different.
>
> Please can you be more specific? I'm still learning Subversion.
> Thanks.

'svn revert' undoes any local changes you've made to your working
copy. It does this by overwriting your working files with 'pristine'
copies that are stashed away in the .svn/ areas.

See the Handbook... in particular, the "Basic Work Cycle" section:

http://subversion.tigris.org/files/documents/15/576/svn-handbook.html#Basic%20Work%20Cycle

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 30 06:06:16 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.