Yes, you are correct, I can do what you suggest. It just feels wierd to carry
that property on all versions of the directory when I would really ever need
the latest.... although I guess it could be interesting to document the
life-cycle of a particular branch by following the transitions of the
Just curious, is anyone else doing something like this. I had put a system in
place with ClearCase at my last job (BEFORE they put UCM in there) and it
worked really well. All branches were reviewed before they got merged, all
the merges were automated and everything was on the web...
If I get all this working with subversion would anybody else be interested in
On November 8, 2002 10:47 am, Noel Yap wrote:
> --- Greg Dickie <email@example.com> wrote:
> > Well it just doesn't make much sense to me I guess.
> > If I want to know what
> > state a branch is in for example ( working,
> > ready_for_review,
> > rejected,approved ) where would I look for that? I
> > guess I could make it work
> > but then I'd be carrying those properties over on
> > each subversion of the
> > branch directory....
> Maybe I don't quite understand the problem. It sounds
> like you should be able to query for the value of the
> property on the HEAD version of the branch. Am I
> missing something?
> OTOH, from your last sentence above, and the fact that
> you mentioned ClearCase in your prior email, you may
> be under the impression that Subversion will have
> versions under the branches like the following:
> Instead, Subversion versions the /entire/ repository
> so you really get something like:
> Please excuse and correct me if I'm making incorrect
> assumptions on your knowledge.
> Do you Yahoo!?
> U2 on LAUNCH - Exclusive greatest hits videos
just a guy
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Nov 8 17:07:39 2002