bk commit into 5.0 tree (elliot:1.2207)

[Elliot Murphy]

Below is the list of changes that have just been committed into a local
5.0 repository of emurphy. When emurphy does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html

ChangeSet
  1.2207 06/06/23 16:13:57 elliot@stripped +2 -0
  Adding a commit template and a trigger to clean the 
  standard comments out of the commit messages.
  

  BitKeeper/templates/commit
    1.1 06/06/23 16:13:54 elliot@stripped +6 -0
    New commit message template

  BitKeeper/triggers/pre-commit.cset_comments
    1.3 06/06/23 16:13:54 elliot@stripped +1 -1
    Fixing the path for the temporary comment file
    Adding missing > for sed pattern

  BitKeeper/templates/commit
    1.0 06/06/23 16:13:54 elliot@stripped +0 -0
    BitKeeper file /home/emurphy/src/mysql/mysql-5.0-maint/BitKeeper/templates/commit

  BitKeeper/triggers/pre-commit.cset_comments
    1.2 06/06/23 15:56:17 elliot@stripped +1 -2
    Removed newline that was causing trigger to fail.

  BitKeeper/triggers/pre-commit.cset_comments
    1.1 06/06/23 15:54:56 elliot@stripped +11 -0
    Trigger for stripping default text out of comments
    (stuff that was contained in the commit template)

  BitKeeper/triggers/pre-commit.cset_comments
    1.0 06/06/23 15:54:56 elliot@stripped +0 -0
    BitKeeper file
/home/emurphy/src/mysql/mysql-5.0-maint/BitKeeper/triggers/pre-commit.cset_comments

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	elliot
# Host:	scared.(none)
# Root:	/home/emurphy/src/mysql/mysql-5.0-maint
--- New file ---
+++ BitKeeper/templates/commit	06/06/23 16:13:54

>  Lines beginning with '>  ' will be removed automatically
>  Please be sure to specify BUG#NNNN or WL#NNNN in your
>  changeset comment. The changeset comment should describe
>  at a high level the problem that your changes solve, rather
>  than simply describing the code that was changed.

--- New file ---
+++ BitKeeper/triggers/pre-commit.cset_comments	06/06/23 15:54:56
#!/bin/sh
#
# Using pre-commit trigger to strip default
# text out of changeset comment
# BitKeeper/trigger/pre-commit.cset_comments
#
# This is safe on Windows because BK includes
# sed internally so triggers may use it
#
mv $BK_COMMENTFILE tmp_comment && sed -e '/^>  /d' tmp_comment >
$BK_COMMENTFILE && rm -f tmp_comment