[Python-checkins] CVS: python/nondist/sf-html sf-faq.html,1.11,1.12

[Peter Schneider-Kamp]

Update of /cvsroot/python/python/nondist/sf-html
In directory slayer.i.sourceforge.net:/tmp/cvs-serv14417

Modified Files:
	sf-faq.html 
Log Message:

added question about forcing a branch tag on files



Index: sf-faq.html
===================================================================
RCS file: /cvsroot/python/python/nondist/sf-html/sf-faq.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -C2 -r1.11 -r1.12
*** sf-faq.html	2000/07/25 10:39:58	1.11
--- sf-faq.html	2000/08/10 03:51:09	1.12
***************
*** 35,38 ****
--- 35,39 ----
    <li><a href="#c6">How to revert changes?</a></li>
    <li><a href="#c7">How to add binary files?</a></li>
+   <li><a href="#c8">How to force a branch tag on a file?</a></li>
  </ol>
  
***************
*** 342,345 ****
--- 343,362 ----
    <tt>cvs commit newfile.bin</tt><br />
  </blockquote>
+ 
+ <h3><a name="c8" id="c8"></a>2.8.:</h3>
+ 
+ <h4>Q: How to force a branch tag on a file?</h4>
+ 
+ <h4>A:</h4>
+ The quickest way to force a branch tag <tt>branch_tag</tt> on a file is to
+ issue the command
+ 
+ <blockquote>
+   <tt>cvs tag -F -b -r revision branch_tag file</tt><br />
+ </blockquote>
+ for each file, where <tt>revision</tt> is the revision where the tag should be
+ and <tt>file</tt> is the file.  Note that -F means <tt>force</tt> (otherwise
+ you get a complaint because the tag is already defined) and -b means
+ <tt>branch</tt> which makes the tag a branch tag.
  
  <h1><a name="patches" id="patches"></a>3. Patches</h1>