From: "Magnus Bäck" <baeck@google.com>
To: Joydeep Bakshi <joydeep.bakshi@infoservices.in>
Cc: git@vger.kernel.org
Subject: Re: git branch based hook desigh
Date: Wed, 20 Mar 2013 09:46:32 -0400 [thread overview]
Message-ID: <20130320134631.GA7325@google.com> (raw)
In-Reply-To: <148C5E2E-8FD6-4686-A009-57D1F403C808@infoservices.in>
On Monday, March 18, 2013 at 00:27 EDT,
Joydeep Bakshi <joydeep.bakshi@infoservices.in> wrote:
> I have implemented git pre-received hook successfully. And it works on
> the repo level.
> Could anyone suggest how to call branch level hook please ?--
If you need to have different hook behaviors depending on the ref that's
about to be updated, just put a conditional in the hook. You get the
name(s) of ref(s) to be updated on stdin.
--
Magnus Bäck
baeck@google.com
prev parent reply other threads:[~2013-03-20 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 4:27 git branch based hook desigh Joydeep Bakshi
2013-03-20 13:46 ` Magnus Bäck [this message]
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=20130320134631.GA7325@google.com \
--to=baeck@google.com \
--cc=git@vger.kernel.org \
--cc=joydeep.bakshi@infoservices.in \
/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).