[m-dev.] for review: add "Branches" field to CVS log template

Fergus Henderson fjh at cs.mu.OZ.AU
Thu Mar 1 23:38:57 AEDT 2001


Hi,

Everyone (myself included) seems to be regularly forgetting to say
which branch(es) each change is intended for.

So I propose to include a "Branches" field in the CVS log template.
This is not particularly useful within CVS itself, since CVS
automatically records which branch the change is on.  But I think it
would be very useful when posting changes to mercury-developers.

The idea is that for the main and release branches, we'd fill in this
field with a slightly more abstract value that the actual cvs branch,
e.g. `release' instead of `version-0_10_y' and `main' instead of `HEAD'.

For example:

	Branches: main
	Branches: release
	Branches: main and release
	Branches: reuse
	Branches: alias

Comments?

----------

Estimated hours taken: 0.25
Branches: main

CVSROOT/log_template:
	Add a new "branches" field.

Workspace: /mnt/munginya/home/pgrad/fjh/cvs
Index: CVSROOT/log_template
===================================================================
RCS file: /home/staff/zs/imp/CVSROOT/log_template,v
retrieving revision 1.5
diff -u -d -r1.5 log_template
--- CVSROOT/log_template	1997/07/16 07:09:16	1.5
+++ CVSROOT/log_template	2001/03/01 12:27:29
@@ -1,5 +1,7 @@
 
 Estimated hours taken: _____
+Branches: <which CVS branches ("main", "release", etc.) this change
+           will be committed on>
 
 <overview or general description of changes>
 

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
                                    |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------



More information about the developers mailing list