[Buildbot-commits] buildbot/docs buildbot.texinfo,1.123,1.124

[Brian Warner]

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

Modified Files:
	buildbot.texinfo 
Log Message:
[project @ web: handle branch=trunk usefully]

Original author: warner at lothar.com
Date: 2007-09-30 09:23:10+00:00

Index: buildbot.texinfo
===================================================================
RCS file: /cvsroot/buildbot/buildbot/docs/buildbot.texinfo,v
retrieving revision 1.123
retrieving revision 1.124
diff -u -d -r1.123 -r1.124
--- buildbot.texinfo	30 Sep 2007 08:30:23 -0000	1.123
+++ buildbot.texinfo	30 Sep 2007 09:24:03 -0000	1.124
@@ -6083,16 +6083,13 @@
 
 The @code{branch=} query argument can be used on some pages. This
 filters the information displayed by that page down to only the builds
-or changes which involved the given branch. Multiple @code{branch=}
-arguments can be used to examine multiple branches at once (so
-appending @code{?branch=foo&branch=bar} to the URL will show builds
-involving either branch). No @code{branch=} arguments means to show
-builds and changes for all branches.
-
-Note that branch-handling still needs to be cleaned up: in particular
-there is currently no way to refer to the default (or ``trunk'')
-branch using @code{branch=} arguments. This will be improved in a
-future release.
+or changes which involved the given branch. Use @code{branch=trunk} to
+reference the trunk: if you aren't intentionally using branches,
+you're probably using trunk. Multiple @code{branch=} arguments can be
+used to examine multiple branches at once (so appending
+ at code{?branch=foo&branch=bar} to the URL will show builds involving
+either branch). No @code{branch=} arguments means to show builds and
+changes for all branches.
 
 Some pages may include the Builder name or the build number in the
 main part of the URL itself. For example, a page that describes Build