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

Re: Defining branch life-cycles in subversion

From: Noel Yap <yap_noel_at_yahoo.com>
Date: 2002-11-08 17:21:32 CET

--- Greg Dickie <greg@max-t.com> wrote:
> My problem with what what you suggest is that it
> seems like overkill. I need a
> perty onthe overall branch, not every version of the
> branch. If I wanted to
> know what state a particular branch was in would I
> just do "propget status -r
> HEAD
> http://svn.dodo.da/repos/mm/branches/greg-work3" ?

I think you 'know' how Subversion works, but you still
haven't grok'ed the full meaning of versioning the
entire repository.

If you don't mind, I'll step through it (for my sake
as much as for yours ;-)

Each time there's a commit, the /entire/ repository is
versioned. Logically, you can view this as the entire
repository is copied, then the commited change made to
the copy. Physically, it's much more efficient than
that, of course.

So, the HEAD revision /of/, rather than on, the branch
(which, as you know, is just a directory) will have
the latest value of the property. So, the fact that
each version of the branch has the property set should
cause no problems or concerns. In fact, it would give
you the ability to query the state of the branch at
each of its revisions.

HTH,
Noel

__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 8 17:22:17 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.