From: Jan Hudec <bulb@ucw.cz>
To: Andreas Ericsson <ae@op5.se>
Cc: Kristis Makris <kristis.makris@asu.edu>,
Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: Git and tagging hook
Date: Tue, 14 Oct 2008 19:22:27 +0200 [thread overview]
Message-ID: <20081014172227.GB6931@efreet.light.src> (raw)
In-Reply-To: <48ECF072.3000506@op5.se>
On Wed, Oct 08, 2008 at 19:40:02 +0200, Andreas Ericsson wrote:
> Kristis Makris wrote:
>> On Tue, 2008-10-07 at 19:28 +0200, Jakub Narebski wrote:
>>> Kristis Makris wrote:
>>>> I want the integration when I apply the tag to a local repository, NOT
>>>> only when I push/pull.
Care to explain why that would ever be useful? It's local, which means that:
- the user can take it back without a trace it ever happened (git tag -d or
even git update-ref -d) and
- noone except the user will see it anyway, so it's not like they should
care either.
Besides, you don't need git tag to create a tag in git, so the hook wouldn't
really be guaranteed anyway (I mean, just like the commit hook is not -- you
can still commit by calling write-tree, commit-tree and update-ref and avoid
the hook).
>>> If you are talking about taging locally, you can simply make an alias
>>> or do something after tagging. Search archives for description when
>>> it is worth to add a hook, and when it is not.
>>
>> I am looking for a guarantee that is better than casually saying
>> "simply". I will be providing the integration work to users that may not
>> be as comfortable with making aliases.
>>
>> I still don't see why a hook on local tagging is not available. Is it
>> possible to add support in Git for such a hook ? Both pre-tag and
>> post-tag.
>
> Because noone's ever needed one before. If aliases can't do what you
> want, write a patch to support it and hope Junio accepts it. It's really
> quite straight-forward. Make sure you read Documentation/SubmittingPatches
> before you send it.
>
> Note though that use of tags on the developer's side will still be up
> to the developer and not something you can force through other means
> than policy or convention.
Being possible was never a reason to add features to git and the less it was
a reason to add hooks. And there does not seem to be a use-case that would
clearly benefit from having such hooks, or at least none was shown on the
list so far.
For integration with issue tracker, the local tag is neither final, nor
useful to anybody except the user who did it until it hits the central
repository. And working on the central repository directly does not seem like
a good idea either.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
next prev parent reply other threads:[~2008-10-14 17:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 4:45 Git and tagging hook Kristis Makris
2008-10-06 7:17 ` Andreas Ericsson
2008-10-07 17:13 ` Kristis Makris
2008-10-07 17:28 ` Jakub Narebski
2008-10-08 16:47 ` Kristis Makris
2008-10-08 17:40 ` Andreas Ericsson
2008-10-14 17:22 ` Jan Hudec [this message]
[not found] ` <20081014172227.GB6931-hYs7FtC5zV+YSD4dQj0czg@public.gmane.org>
2008-10-14 18:03 ` Kristis Makris
2008-10-14 20:49 ` Andreas Ericsson
2008-10-14 21:33 ` Daniel Barkalow
2008-10-16 20:15 ` Jan Hudec
2008-10-17 7:04 ` Andreas Ericsson
2008-10-06 7:20 ` Andreas Ericsson
2008-10-07 17:30 ` Kristis Makris
2008-10-08 6:12 ` Andreas Ericsson
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=20081014172227.GB6931@efreet.light.src \
--to=bulb@ucw.cz \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=kristis.makris@asu.edu \
/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).