From: Christian Couder <chriscool@tuxfamily.org>
To: Junio Hamano <junkio@cox.net>, Pieter de Bie <pdebie@ai.rug.nl>,
Jakub Narebski <jnareb@gmail.com>,
Manoj Srivastava <srivasta@ieee.org>,
"Thomas Adam" <thomas.adam22@gmail.com>
Cc: git@vger.kernel.org
Subject: [PATCH 1/3] Documentation: hooks: fix missing verb in pre-applypatch description
Date: Fri, 2 May 2008 05:30:41 +0200 [thread overview]
Message-ID: <20080502053041.c526250c.chriscool@tuxfamily.org> (raw)
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
Documentation/hooks.txt | 9 +++++----
1 files changed, 5 insertions(+), 4 deletions(-)
Here is a patch series with my current "Documentation"
improvements.
The changes since the last patches are the following:
- move fix to "hooks" before other changes
- fix links to the renamed "githooks" (patch 2/3)
- rename and convert to man pages some tutorials
(new patch 3/3)
diff --git a/Documentation/hooks.txt b/Documentation/hooks.txt
index 44fbe58..1283ab4 100644
--- a/Documentation/hooks.txt
+++ b/Documentation/hooks.txt
@@ -28,10 +28,11 @@ The default 'applypatch-msg' hook, when enabled, runs the
pre-applypatch
--------------
-This hook is invoked by `git-am`. It takes no parameter,
-and is invoked after the patch is applied, but before a commit
-is made. Exiting with non-zero status causes the working tree
-after application of the patch not committed.
+This hook is invoked by `git-am`. It takes no parameter, and is
+invoked after the patch is applied, but before a commit is made.
+
+If it exits with non-zero status, then the working tree will not be
+committed after applying the patch.
It can be used to inspect the current working tree and refuse to
make a commit if it does not pass certain test.
--
1.5.5.1.124.g7e5fa.dirty
reply other threads:[~2008-05-02 3:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080502053041.c526250c.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=junkio@cox.net \
--cc=pdebie@ai.rug.nl \
--cc=srivasta@ieee.org \
--cc=thomas.adam22@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).