1<div id="Committing-to-a-branch"></div> 2<div class="header"> 3<p> 4 |[[cvs: Index#SEC_Contents|Contents]]||[[cvs: Index#Index|Index]]|</p> 5</div> 6 7---- 8 9===== Committing to a branch ===== 10 11You can commit to a branch revision (one that has an 12even number of dots) with the ‘<code>-r</code>’ option. To 13create a branch revision, use the ‘<code>-b</code>’ option 14of the <code>rtag</code> or <code>tag</code> commands 15(see [[cvs: Branching and merging#Branching and merging|Branching and merging]]). Then, either <code>checkout</code> or 16<code>update</code> can be used to base your sources on the 17newly created branch. From that point on, all 18<code>commit</code> changes made within these working sources 19will be automatically added to a branch revision, 20thereby not disturbing main-line development in any 21way. For example, if you had to create a patch to the 221.2 version of the product, even though the 2.0 version 23is already under development, you might do: 24 25<div class="example" style="margin-left: 3.2em"> 26 $ cvs rtag -b -r FCS1_2 FCS1_2_Patch product_module 27 $ cvs checkout -r FCS1_2_Patch product_module 28 $ cd product_module 29 <nowiki>[[</nowiki> hack away <nowiki>]]</nowiki> 30 $ cvs commit 31</div> 32 33This works automatically since the ‘<code>-r</code>’ option is 34sticky. 35 36This document was generated on <i>a sunny day</i> using [http://www.nongnu.org/texi2html/ <i>texi2html</i>]. 37