RE: [Squeak-VMdev] RE: Pending 3.2 and VM sources @ sourceforge

[Rob W. <rwi...@at...>]

gor...@bl... wrote:
> rwi...@at... wrote:
> > our process.  Do we want to complicate it further, 
> > technically, by trying to tackle cvssupport?
> 
> Honestly, no! :-) But we can check it out later.

Whew.  That's good.  :)   My opinion is that we are much better off
using a trust system and minimizing the technical barriers.  We all want
to create the highest quality system we can.
 

> > How far off are we to 3.2final?
> 
> No idea. ;-)

Me neither, but it feels like we are getting close.  What can I do to
help cvsproj and sqcvs along?

> Since you tagged those on the line above I assume you still have those
> revisions :-) so the "-r 3.2g" is actually unnecessary (but correct).

Note that this has been a hypothetical; I didn't actually tag the unix
stuff as I feel that that is Lex's or Ian's perogative.  

There could be a lot of branches off of the trunk, which could get
unweildy with all of the Root-of-XXX.  I like John's approach of using a
<major>.<minor>.<patch>.0 (i.e. 3.2.7.0), then branches could be
<major>.<minor>.<patch>.<branch>...(<subbranch>)  (i.e. 3.2.7.1).  I
suppose we could even tag a particular revision of a branch as the root
of a subbranch, like 3.2.7.1.0, and the subbranch would be 3.2.7.1.1 and
so on.

> There is also the command "rtag" that can tag stuff without having a
> workingcopy but I never use that - I feel in more control with "tag".

I agree, especially given your discussion of verifying with cvs update.

> > to checkout the branch:
> > 
> > cvs checkout -r 3.2g-experimental-protected-memory
> 
> Yes, this would check out the tip of the branch. This will place a so
> called "sticky tag" on your files in your workingcopy so that all
> operations from now on happen on the branch. Quite convenient. 

I see.  Now you won't be affecting the trunk at all.

> You can
> also move an existing checked out trunk onto the branch by using:
> cvs update -r 3.2g-experimental-protected-memory

hmmm.  I don't follow you here.  What exactly does this do?  Oh.  Are
you saying that if I have done

cvs co -r 3.2g

then I could do 

cvs up -r 3.2g-experimental-protected-memory

and my working copy will now be the latest in the branched tipped with
3.2g-experimental-protected-memory?
  
> This would have the same result as the checkout but with much less IO.
> And moving it back to the trunk is done by clearing the sticky tag:
> 
> cvs update -A

Will this take the latest from the trunk, or the root?

> My impression is that LinCVS is a poor clone of WinCVS/MacCVS (which are
> pretty good by now). TkCVS looks interesting and has more advanced
> features.

Very nice - I am d/ling tkcvs as I write this.

thanks and cheers,
Rob