From: Joey Hess <joey@kitenet.net>
To: Eric Raymond <esr@thyrsus.com>
Cc: git@vger.kernel.org
Subject: ciabot scripts and merge flood prevention
Date: Sat, 24 Apr 2010 11:05:11 -0400 [thread overview]
Message-ID: <20100424150511.GA7318@gnu.kitenet.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
There's a problem with the old ciabot scripts, and I think also the v3
versions, when two published branches are merged. In this case, ciabot
reports all the changes twice, once when they're first committed to the
first branch, and a second time when the first branch is merged into the
second. This can unleash a flood of redundant commit messages that wipes
out conversation in any poor irc channel that has CIA in it. I've
generated floods that lasted up to 15 minutes.
I document the problem and one solution here. There's also a link to
the hook script Gnome is using, based on the same method.
http://kitenet.net/~joey/blog/entry/lazyweb:_git_cia_hooks/
Maybe this could be built into the ciabot scripts?
(BTW, in both scripts, the example of git-rev-list ... | tac
could perhaps more efficiently be written as git-rev-list --reverse ...)
--
see shy jo
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next reply other threads:[~2010-04-24 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 15:05 Joey Hess [this message]
2010-04-24 16:05 ` ciabot scripts and merge flood prevention Eric Raymond
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=20100424150511.GA7318@gnu.kitenet.net \
--to=joey@kitenet.net \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
/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).