git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pat Notz <patnotz@gmail.com>
To: Ammon Riley <ammon.riley@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [PATCH] Add a post-tag hook
Date: Fri, 24 Apr 2009 10:41:47 -0600	[thread overview]
Message-ID: <1cd1989b0904240941o3d80bdbby19fb02093c887af@mail.gmail.com> (raw)
In-Reply-To: <cd3664ac0904171528p3ed55071p4e098f5181fb0b27@mail.gmail.com>

On Fri, Apr 17, 2009 at 4:28 PM, Ammon Riley <ammon.riley@gmail.com> wrote:
>
> On Fri, Apr 17, 2009 at 3:19 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
> > Ammon Riley <ammon.riley@gmail.com> wrote:
> >> Add a post-tag hook, to allow notifications when a tag is created.
> >> The hook is given the name of the newly created tag.
> >
> > Why would you want to send notifications upon creating a tag in
> > your local repository?
> >
> > Usually a tag is only interesting when it has been sent to a shared
> > public repository, which is by git push, and thus is caught by a
> > git receive-pack hook like post-update or post-receive.
>
> On the particular project I'm working on, we're not really using git
> in the most distributed fashion -- it's completely internal to the
> company. In our case, the tags are being created directly on
> the shared repository, rather than on a local repository and being
> pushed.

Today, this same situation came up in my organization.  It seem like a
natural partner of the post-commit hook.

>
> Cheers,
> Ammon
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-04-24 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 22:15 [PATCH] Add a post-tag hook Ammon Riley
2009-04-17 22:19 ` Shawn O. Pearce
2009-04-17 22:28   ` Ammon Riley
2009-04-24 16:41     ` Pat Notz [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=1cd1989b0904240941o3d80bdbby19fb02093c887af@mail.gmail.com \
    --to=patnotz@gmail.com \
    --cc=ammon.riley@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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).