git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dun Peal <dunpealer@gmail.com>
To: git@vger.kernel.org
Subject: Git version of some common SVN hooks?
Date: Mon, 4 Oct 2010 14:43:45 -0500	[thread overview]
Message-ID: <AANLkTimPGtH9xCh8rLSMAa2KDNOEDUt49qFK7p==aZho@mail.gmail.com> (raw)

Hi,

I'm porting a large and active repository from SVN to Git.

To provide the developers with the same features, I need the Git
version of the following common hooks:

1. svn2cl: the Subversion ChangeLog Generator. Basically a script that
sends a readable email listing a range of commits, showing just a
short summary for each commit: author name, timestamp, hash, paths
modified, commit message.
2. Hook to reject any commit containing a path with non-ASCII characters.
3. Hook to reject any commit causing the repository to contain two or
more paths that differ from each other only in letter case. For
instance, a commit adding foo/bar.py would be rejected if foo/Bar.py
was added as part of that same commit, or already existed in the repo.
4. Hook to trigger an action based on which path was committed to. For
example, if a developer commits into REPO_ROOT/foo, send an email to
address foo@somedomain, whereas a commit to REPO_ROOT/bar will send an
email to bar@somedomain.

I'm hoping there are Git versions of these hooks already written, but
if now any leads about implementing them would be appreciated.

Our full setup btw is a large repository hosted on a local instance of
Gitorious. All our users use Git >= 1.7, although they work on all 3
operating systems: Linux, OS X, Windows.

Thanks, D

             reply	other threads:[~2010-10-04 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 19:43 Dun Peal [this message]
2010-10-04 20:58 ` Git version of some common SVN hooks? Chris Packham

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='AANLkTimPGtH9xCh8rLSMAa2KDNOEDUt49qFK7p==aZho@mail.gmail.com' \
    --to=dunpealer@gmail.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).