From: Johannes Sixt <j6t@kdbg.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Neal Kreitzinger <nkreitzinger@gmail.com>,
Adrian Cornish <git@bluedreamer.com>
Subject: Re: [PATCH 1/(3/4)] test: does pre-commit-hook learn authorship?
Date: Sun, 11 Mar 2012 21:30:08 +0100 [thread overview]
Message-ID: <4F5D0B50.20803@kdbg.org> (raw)
In-Reply-To: <7v1uozz97f.fsf_-_@alter.siamese.dyndns.org>
Am 11.03.2012 12:08, schrieb Junio C Hamano:
> +test_expect_failure 'check the author in hook' '
> + cat >"$HOOK" <<-\EOF &&
> + test "$GIT_AUTHOR_NAME" = "New Author" &&
> + test "$GIT_AUTHOR_EMAIL" = "newauthor@example.com"
> + EOF
Please insert #!/bin/sh as the first line of the script. We'll need it
on Windows.
-- Hannes
next prev parent reply other threads:[~2012-03-11 20:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 1:15 Stop a git commit by a specific author using pre-commit hook Adrian Cornish
2012-03-10 19:41 ` Neal Kreitzinger
2012-03-10 21:54 ` Junio C Hamano
2012-03-10 23:03 ` Neal Kreitzinger
2012-03-11 11:05 ` Junio C Hamano
2012-03-11 11:08 ` [PATCH 1/(3/4)] test: does pre-commit-hook learn authorship? Junio C Hamano
2012-03-11 20:30 ` Johannes Sixt [this message]
2012-03-11 21:09 ` Junio C Hamano
2012-03-11 11:09 ` [PATCH 2/(3/4)] ident.c: add split_ident_line() to parse formatted ident line Junio C Hamano
2012-03-11 11:11 ` [PATCH 3/3] commit: pass author/committer info to hooks Junio C Hamano
2012-03-12 11:29 ` Jeff King
2012-03-11 11:15 ` [PATCH 3/4] run_hook(): enhance the interface to pass arbitrary environment Junio C Hamano
2012-03-11 11:16 ` [PATCH 4/4] commit: pass author/committer info to hooks Junio C Hamano
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=4F5D0B50.20803@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@bluedreamer.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nkreitzinger@gmail.com \
/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).