Eric Niebler wrote:
I've never used TortoiseCVS, so I don't know. I use cvs and follow the release procedures described at http://boost.org/more/release_procedures.htm. I never merge more than the files I'm working on.
Thanks for the link. This will help me as well, as I made a mistake somewhere when integrating the boost/Jamfile.v2 fix for the serialization libraries. Do you know how merged_to_RC_1_34_0 gets updated into the RC_1_34_0?
Don't forget to "cvs tag" when you're done merging your changed into RC_1_34_0.
I think I missed that. Shouldn't it be merged_to_RC_1_34_0 instead of RC_1_34_0 when running cvs tag? Do you mean something like: cvs ... # merge changes and resolve conflicts cvs tag -c merged_to_RC_1_34_0 # update merged_to_RC_1_34_0 branch ... # repeat cvs tag -c RC_1_34_0 # we are done, so update RC_1_34_0 ? - Reece _________________________________________________________________ Try Live.com - your fast, personalized homepage with all the things you care about in one place. http://www.live.com/getstarted