On Oct 30, 2006, at 2:59 PM, Miller Puckette wrote:

I just checked out a version and made it branch as in:

cvs tag -r stable_0_40 v0-40-0

That looks like it creates a tag rather than a branch. That URL said to do this to create a branch:

cvs rtag -b -r release-1-0 release-1-0-patches tc

With "-b" making a branch.

http://docs.freebsd.org/info/cvs/cvs.info.Creating_a_branch.html

.hc

then make changes and commit like this:

cvs commit -r stable_0_40 pd

This was following instructions I found on the very readable into: http://docs.freebsd.org/info/cvs/cvs.info.Top.html

cheers Miller

On Mon, Oct 30, 2006 at 02:52:04PM -0500, Hans-Christoph Steiner wrote:

...

Anyone have any good advice on making a branch in CVS? Or perhaps a good HOWTO? Its time to make a branch for the Pd-0.39.2-extended release.

.hc

---

---

As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin

---

PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev

------------------------------------------------------------------------

All information should be free. - the hacker ethic

On Oct 30, 2006, at 3:24 PM, IOhannes m zmölnig wrote:

Hans-Christoph Steiner wrote:

...

Anyone have any good advice on making a branch in CVS? Or perhaps a good HOWTO? Its time to make a branch for the Pd-0.39.2- extended release.

what is your exact problem?

how does "cvs tag -b extended_0_39_2" (within the cvsroot) not fit your needs?

btw, googling for "cvs tag" returned http://www.psc.edu/~semke/ cvs_branches.html as the second hit (the first one was a dead link)

there is no magic involved in tagging.

btw, i thought someone mentioned a "best practice CVS" document a while ago ;-)

I know tagging, that's dead simple. I am talking about a branch. I can google "cvs tag" or "cvs branch" myself too, but a personal recommendation is worth a lot more than a google search.

I am more interested in experience in managing changes in the branch. Some changes should get folded in to MAIN, others are only for the branch. I am sure there are things that you can do that will make your life easier when the time to merge comes.

.hc

------------------------------------------------------------------------

All information should be free. - the hacker ethic