From: Joey Hess <joey@kitenet.net>
To: git@vger.kernel.org
Subject: extended hook api and tweak-fetch hook
Date: Thu, 29 Dec 2011 21:07:17 -0400 [thread overview]
Message-ID: <1325207240-22622-1-git-send-email-joey@kitenet.net> (raw)
This patch series adds an extended hook API, and uses it to implement
the new tweak-fetch hook.
The remaining hooks (that do not already use run_hook()) could be
refactored later to use this new API.
Also, the API has been designed to allow several programs to be run
for a single hook, when someone wants to add that into git.
next reply other threads:[~2011-12-30 2:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 1:07 Joey Hess [this message]
2011-12-30 1:07 ` [PATCH 1/3] expanded hook api with stdio support Joey Hess
2011-12-30 9:47 ` Johannes Sixt
2011-12-30 17:13 ` Joey Hess
2011-12-30 18:04 ` Johannes Sixt
2012-01-03 19:53 ` Junio C Hamano
2012-01-03 20:06 ` Jeff King
2012-01-03 21:44 ` Junio C Hamano
2011-12-30 1:07 ` [PATCH 2/3] preparations for tweak-fetch hook Joey Hess
2011-12-30 1:07 ` [PATCH 3/3] add " Joey Hess
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=1325207240-22622-1-git-send-email-joey@kitenet.net \
--to=joey@kitenet.net \
--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).