[PATCH] Remove ciabot from contrib

2013-09-26 Thread Stefan Beller
According to
http://thread.gmane.org/gmane.comp.version-control.git/212649
Eric, the original author of ciabot, doesn't want the ciabot
no longer be included in git.git, hence the removal of the
whole directory.

Signed-off-by: Stefan Beller stefanbel...@googlemail.com
---

I found out about this task by browsing 
http://git-blame.blogspot.de/search?q=leftover


 contrib/ciabot/INSTALL   |  54 --
 contrib/ciabot/README|  11 --
 contrib/ciabot/ciabot.py | 255 ---
 contrib/ciabot/ciabot.sh | 233 ---
 4 files changed, 553 deletions(-)
 delete mode 100644 contrib/ciabot/INSTALL
 delete mode 100644 contrib/ciabot/README
 delete mode 100755 contrib/ciabot/ciabot.py
 delete mode 100755 contrib/ciabot/ciabot.sh

diff --git a/contrib/ciabot/INSTALL b/contrib/ciabot/INSTALL
deleted file mode 100644
index 7222961..000
--- a/contrib/ciabot/INSTALL
+++ /dev/null
@@ -1,54 +0,0 @@
-= Installation instructions =
-
-Two scripts are included.  The Python one (ciabot.py) is faster and
-more capable; the shell one (ciabot.sh) is a fallback in case Python
-gives your git hosting site indigestion. (I know of no such sites.)
-
-It is no longer necessary to modify the script in order to put it
-in place; in fact, this is now discouraged. It is entirely
-configurable with the following git config variables:
-
-ciabot.project = name of the project
-ciabot.repo = name of the project repo for gitweb/cgit purposes
-ciabot.xmlrpc  = if true, ship notifications via XML-RPC
-ciabot.revformat = format in which the revision is shown
-
-The revformat variable may have the following values
-raw - full hex ID of commit
-short - first 12 chars of hex ID
-describe - describe relative to last tag, falling back to short
-
-ciabot.project defaults to the directory name of the repository toplevel.
-ciabot.repo defaults to ciabot.project lowercased.
-ciabot.xmlrpc defaults to True
-ciabot.revformat defaults to 'describe'.
-
-This means that in the normal case you need not do any configuration at all,
-however setting ciabot.project will allow the hook to run slightly faster.
-
-Once you've set these variables, try your script with -n to see the
-notification message dumped to stdout and verify that it looks sane.
-
-To live-test these scripts, your project needs to have been registered with
-the CIA site.  Here are the steps:
-
-1. Open an IRC window on irc://freenode/commits or your registered
-   project IRC channel.
-
-2. Run ciabot.py and/or ciabot.sh from any directory under git
-   control.
-
-You should see a notification on the channel for your most recent commit.
-
-After verifying correct function, install one of these scripts either
-in a post-commit hook or in an update hook.
-
-In post-commit, run it without arguments. It will query for
-current HEAD and the latest commit ID to get the information it
-needs.
-
-In update, call it with a refname followed by a list of commits:
-You want to reverse the order git rev-list emits because it lists
-from most recent to oldest.
-
-/path/to/ciabot.py ${refname} $(git rev-list ${oldhead}..${newhead} | tac)
diff --git a/contrib/ciabot/README b/contrib/ciabot/README
deleted file mode 100644
index 2dfe1f9..000
--- a/contrib/ciabot/README
+++ /dev/null
@@ -1,11 +0,0 @@
-These are hook scripts for the CIA notification service at http://cia.vc/
-
-They are maintained by Eric S. Raymond e...@thyrsus.com.  There is an
-upstream resource page for them at http://www.catb.org/esr/ciabot/,
-but they are unlikely to change rapidly.
-
-You probably want the Python version; it's faster, more capable, and
-better documented.  The shell version is maintained only as a fallback
-for use on hosting sites that don't permit Python hook scripts.
-
-See the file INSTALL for installation instructions.
diff --git a/contrib/ciabot/ciabot.py b/contrib/ciabot/ciabot.py
deleted file mode 100755
index befa0c3..000
--- a/contrib/ciabot/ciabot.py
+++ /dev/null
@@ -1,255 +0,0 @@
-#!/usr/bin/env python
-# Copyright (c) 2010 Eric S. Raymond e...@thyrsus.com
-# Distributed under BSD terms.
-#
-# This script contains porcelain and porcelain byproducts.
-# It's Python because the Python standard libraries avoid portability/security
-# issues raised by callouts in the ancestral Perl and sh scripts.  It should
-# be compatible back to Python 2.1.5
-#
-# usage: ciabot.py [-V] [-n] [-p projectname]  [refname [commits...]]
-#
-# This script is meant to be run either in a post-commit hook or in an
-# update hook. Try it with -n to see the notification mail dumped to
-# stdout and verify that it looks sane. With -V it dumps its version
-# and exits.
-#
-# In post-commit, run it without arguments. It will query for
-# current HEAD and the latest commit ID to get the information it
-# needs.
-#
-# In update, call it with a refname followed by a list of commits:
-# You want to reverse the order git rev-list emits because it lists
-# from 

Re: [PATCH] Remove ciabot from contrib

2013-09-26 Thread Keshav Kini
Stefan Beller stefanbel...@googlemail.com writes:

 According to
 http://thread.gmane.org/gmane.comp.version-control.git/212649
 Eric, the original author of ciabot, doesn't want the ciabot
 no longer be included in git.git, hence the removal of the
 whole directory.

I take it you mean that he doesn't want the ciabot *any* longer be
included in git.git, right? I would rephrase it as follows:

Eric, the original author of ciabot, no longer wants the ciabot to
be included in git.git, hence the removal of the whole directory.

See http://thread.gmane.org/gmane.comp.version-control.git/212649 .

-Keshav

--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH] Remove ciabot from contrib

2013-09-26 Thread Eric S. Raymond
Stefan Beller stefanbel...@googlemail.com:
 According to
 http://thread.gmane.org/gmane.comp.version-control.git/212649
 Eric, the original author of ciabot, doesn't want the ciabot
 no longer be included in git.git, hence the removal of the
 whole directory.

Note: I was *not* the original author of the ciabot scripts.  I was
their maintainer (baton passed to me by the original authors) when
the CIA service irrecoverably crashed, and did suggest they be
removed.  (It is however true that I had rewritten the scripts
pretty heavily, enough so to perhaps be considered a coauthor.)

Junio demurred based on some representations that a development team
not including the CIA author had plans to revive the CIA service.  I said
Wait and see, then - having the ciabot stuff carried in git was
doing me no harm, I was just doing what I thought was my duty by
suggesting the cleanup.

That was almost exactly a year ago now.  The CIA revival effort has since 
sunk without trace.  In part, this is because I fielded a much simpler 
and properly decentralized replacement called irker which is now 
widely enough deployed to have suppressed the demand for CIA.  Repository
hook scripts for irker ship with the irker distribution.

I think enough time has passed that removal would be appropriate.
-- 
a href=http://www.catb.org/~esr/;Eric S. Raymond/a
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH] Remove ciabot from contrib

2013-09-26 Thread Jonathan Nieder
Eric S. Raymond wrote:
 Stefan Beller stefanbel...@googlemail.com:

 According to
 http://thread.gmane.org/gmane.comp.version-control.git/212649
 Eric, the original author of ciabot, doesn't want the ciabot
 no longer be included in git.git, hence the removal of the
 whole directory.

 Note: I was *not* the original author of the ciabot scripts.  I was
 their maintainer (baton passed to me by the original authors) when
 the CIA service irrecoverably crashed, and did suggest they be
 removed.
[...]
 I think enough time has passed that removal would be appropriate.

Thanks, all.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html