From: Jonas Fonseca <fonseca@diku.dk>
To: Petr Baudis <pasky@ucw.cz>, git@vger.kernel.org
Subject: [PATCH] ciabot: fix post-update hook description
Date: Mon, 29 May 2006 02:09:59 +0200 [thread overview]
Message-ID: <20060529000959.GA2061@diku.dk> (raw)
Also, improve on a few lost sentences
Signed-off-by: Jonas Fonseca <fonseca@diku.dk>
---
b2d8b2c5258b6585102c94f37c63dc2360092d87
contrib/ciabot.pl | 30 +++++++++++++++---------------
1 files changed, 15 insertions(+), 15 deletions(-)
b2d8b2c5258b6585102c94f37c63dc2360092d87
diff --git a/contrib/ciabot.pl b/contrib/ciabot.pl
index 83a0d80..e23f5f1 100755
--- a/contrib/ciabot.pl
+++ b/contrib/ciabot.pl
@@ -14,15 +14,15 @@ #
# The master location of this file is in the Cogito repository
# (see http://www.kernel.org/git/).
#
-# This program is designed to run as the .git/commit-post-hook script. It takes
-# the commit information, massaging it and mailing it to the address given below.
+# This program is designed to run as the .git/hooks/post-commit hook. It takes
+# the commit information, massages it and mails it to the address given below.
#
-# The calling convention of the commit-post-hook script is:
+# The calling convention of the post-commit hook is:
#
-# commit-post-hook $commit_sha1 $branch_name
+# .git/hooks/post-commit $commit_sha1 $branch_name
#
# If it does not work, try to disable $xml_rpc in the configuration section
-# below.
+# below. Also, remember to make the hook file executable.
#
#
# Note that you can (and it might be actually more desirable) also use this
@@ -36,9 +36,9 @@ # for merged in $(git-rev-list $newhead
# /path/to/ciabot.pl $merged $refname
# done
#
-# This is useful when you use a remote repository without working copy, where
-# you only push to - the update hook will be trigerred each time you push into
-# that repository, and the pushed commits will be reported through CIA.
+# This is useful when you use a remote repository that you only push to. The
+# update hook will be triggered each time you push into that repository, and
+# the pushed commits will be reported through CIA.
use strict;
use vars qw ($project $from_email $dest_email $noisy $rpc_uri $sendmail
@@ -78,19 +78,19 @@ # not deliver the event at all if CIA se
# unfortunately not an uncommon condition.
$xml_rpc = 0;
-# You can make this bot to totally ignore events concerning the objects
-# specified below. Each object is composed of <path>/<filename>,
+# This variable should contain a regexp, against which each file will be
+# checked, and if the regexp is matched, the file is ignored. This can be
+# useful if you do not want auto-updated files, such as e.g. ChangeLog, to
+# appear via CIA.
#
-# This variable should contain regexp, against which will each object be
-# checked, and if the regexp is matched, the file is ignored. Therefore ie. to
-# ignore all changes in the two files above and everything concerning module
-# 'admin', use:
+# The following example will make the script ignore all changes in two specific
+# files in two different modules, and everything concerning module 'admin':
#
# $ignore_regexp = "^(gentoo/Manifest|elinks/src/bfu/inphist.c|admin/)";
$ignore_regexp = "";
# It can be useful to also grab the generated XML message by some other
-# programs and ie. autogenerate some content based on it. Here you can specify
+# programs and e.g. autogenerate some content based on it. Here you can specify
# a file to which it will be appended.
$alt_local_message_target = "";
--
1.3.3.gd882-dirty
--
Jonas Fonseca
next prev reply other threads:[~2006-05-29 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 0:13 [PATCH] Fix section slicing so help options are not misplaced in cg-commit(1) Jonas Fonseca
2006-05-29 0:12 ` [PATCH] Minor doc fixes Jonas Fonseca
2006-05-29 0:11 ` [PATCH] Portfile: bring it up to date; use description from cogito.spec.in Jonas Fonseca
2006-05-29 0:09 ` Jonas Fonseca [this message]
2006-06-02 21:50 ` [PATCH] ciabot: fix post-update hook description Petr Baudis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060529000959.GA2061@diku.dk \
--to=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).