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

RE: Branching: not getting it

From: <andy.glew_at_amd.com>
Date: 2004-05-03 18:27:42 CEST

> > > And how can a path possibly change? a/b/c
> > > is always going to be a/b/c.
> >
> > Unless it has been svn renamed or copied
> > to a different path.
> You've missed the point, which is that many people use the
> term path to refer to the string, not the object it references, e.g.
> bash> aPath="a/b/c"
> bash> svn mv $aPath a/b/d
> bash> echo $aPath
> a/b/c
> See! It (i.e. aPath) hasn't changed!
> Sorry for being so pedantic

No worries. Further pedantry.

Imagine that there was a function or method which,
given an object, gave you the (or at least a) path
to that object.

Imagine that you had a repository that contained
only one object at HEAD, at that you had an iterator
that allowed you to enumerate over all heads.
(This last is sophistry to allow me to avoid having
to use a path to reference an object.)

Imagine such an iteration

   for all objects O in repo
      print O.path()
   ==> a/b/c

   svn mv a/b/c a/b/d

   for all objects O in repo
      print O.path()
   ==> a/b/d

I'm not objecting to your correction;
I'm jus being a bit more explicit (or pedantic)
about interpretations.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 3 18:28:46 2004

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.