[Buildbot-commits] buildbot/docs buildbot.texinfo,1.5,1.6

[Brian Warner]

Update of /cvsroot/buildbot/buildbot/docs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv9801/docs

Modified Files:
	buildbot.texinfo 
Log Message:
Revision: arch at buildbot.sf.net--2004/buildbot--dev--0--patch-209
Creator:  Brian Warner <warner at monolith.lothar.com>

rename Change(tag=) to branch=

	* buildbot/changes/changes.py: rename tag= to branch=, since
	that's how we're using it, and my design for the upcoming "build a
	specific branch" feature wants it. also, tag= was too CVS-centric
	* buildbot/changes/mail.py (parseSyncmail): same
	* buildbot/process/base.py (Build.isBranchImportant): same
	* buildbot/test/test_mailparse.py (Test3.testMsgS4): same
	* docs/buildbot.texinfo (Attributes of Changes): same

	* NEWS: update tag=, update for upcoming release


Index: buildbot.texinfo
===================================================================
RCS file: /cvsroot/buildbot/buildbot/docs/buildbot.texinfo,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- buildbot.texinfo	17 May 2005 20:04:20 -0000	1.5
+++ buildbot.texinfo	18 May 2005 07:49:30 -0000	1.6
@@ -1090,17 +1090,17 @@
 @code{revision} is an int, the transaction number
 @end table
 
-The Change might also have a @code{tag} attribute. This is primarily
-intended to represent the CVS named branch (since CVS does not embed
-the @code{branch} in the pathname like many of the other systems),
-however it could be used for other purposes as well (e.g. some VC
-systems might allow commits to be marked as @code{cosmetic}, or
-docs-only, or something). The Build, in its @code{isTagImportant}
-method, gets to decide whether the tag is important or not. This
-allows you to configure Builds which only fire on changes to a
-specific branch. For a change to trigger a build, both the @code{tag}
-must be important, and at least one of the files inside the change
-must be considered important.
+The Change might also have a @code{branch} attribute. This is
+primarily intended to represent the CVS named branch (since CVS does
+not embed the @code{branch} in the pathname like many of the other
+systems), however it could be used for other purposes as well (e.g.
+some VC systems might allow commits to be marked as @code{cosmetic},
+or docs-only, or something). The Build, in its
+ at code{isBranchImportant} method, gets to decide whether the branch is
+important or not. This allows you to configure Builds which only fire
+on changes to a specific branch. For a change to trigger a build, both
+the @code{branch} must be important, and at least one of the files
+inside the change must be considered important.