From: Richard Hansen <rhansen@bbn.com>
To: git@vger.kernel.org
Cc: rhansen@bbn.com
Subject: [PATCH 0/2] Documentation/githooks: mention pwd, $GIT_PREFIX
Date: Sat, 10 Jan 2015 01:49:56 -0500 [thread overview]
Message-ID: <1420872598-9609-1-git-send-email-rhansen@bbn.com> (raw)
A couple of patches to document and test that hooks are run from the
top-level directory and that GIT_PREFIX is set to the subdirectory
that Git was run from (like !aliases).
The new documentation is mostly lifted from the documentation for
alias.*. I don't think the new documentation is perfectly clear, but
it's a start. In particular, what does Git do for hook pwd and
GIT_PREFIX when it is run from within a bare repository? Or from
within .git? Or if GIT_WORK_TREE (--work-tree) and/or GIT_DIR
(--git-dir) are set? Many of these same questions apply to !aliases,
so the documentation for alias.* should also be shored up.
-Richard
Richard Hansen (2):
Documentation/githooks: mention pwd, $GIT_PREFIX
t1020-subdirectory.sh: check hook pwd, $GIT_PREFIX
Documentation/githooks.txt | 6 ++++++
t/t1020-subdirectory.sh | 34 ++++++++++++++++++++++++++++++++++
2 files changed, 40 insertions(+)
--
2.2.1
next reply other threads:[~2015-01-10 6:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 6:49 Richard Hansen [this message]
2015-01-10 6:49 ` [PATCH 1/2] Documentation/githooks: mention pwd, $GIT_PREFIX Richard Hansen
2015-01-10 6:49 ` [PATCH 2/2] t1020-subdirectory.sh: check hook " Richard Hansen
2015-01-10 8:25 ` Johannes Sixt
2015-01-10 23:11 ` [PATCH v2 0/2] Documentation/githooks: mention " Richard Hansen
2015-01-10 23:11 ` [PATCH v2 1/2] " Richard Hansen
2015-01-12 19:56 ` Junio C Hamano
2015-01-10 23:11 ` [PATCH v2 2/2] t1020-subdirectory.sh: check hook " Richard Hansen
2015-01-12 22:38 ` 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=1420872598-9609-1-git-send-email-rhansen@bbn.com \
--to=rhansen@bbn.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).