git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kristis Makris <kristis.makris-tTJs1oqo2yY@public.gmane.org>
To: git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: scmbug-users-G8y9j4K4DsPiwOUmbS1EgQ@public.gmane.org
Subject: Git and Scmbug integration
Date: Tue, 13 Nov 2007 12:06:32 -0700	[thread overview]
Message-ID: <1194980792.4106.6.camel@localhost> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1002 bytes --]

Hello,

I've been working on adding Git support in Scmbug, a system that
integrates software configuration management with bug-tracking. I've run
across what seem to be limitations in the Git hooks mechanism (at least
in version 1.5.1.3). In particular:


(1)

http://bugzilla.mkgnu.net/show_bug.cgi?id=991

There's no hook that will trigger when a tag is applied.


(2)

http://bugzilla.mkgnu.net/show_bug.cgi?id=992

Git does not offer metadata describing a change on the commit trigger

The commit trigger seems to be "post-commit" but it supplies no arguments. The
"update" trigger supplies a lot of information but that's only triggered when
changes are published to a remote repository.


I could not find a way to extract this information from what I've read in:

http://www.kernel.org/pub/software/scm/git/docs/hooks.html


Are there plans to implement these hooks ? Or, could someone help me
understand how to extract such information ? 


Thanks,
Kristis

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 188 bytes --]

_______________________________________________
scmbug-users mailing list
scmbug-users-G8y9j4K4DsPiwOUmbS1EgQ@public.gmane.org
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

             reply	other threads:[~2007-11-13 19:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 19:06 Kristis Makris [this message]
2007-11-13 23:00 ` Git and Scmbug integration David Symonds
2007-11-13 23:55   ` Kristis Makris
2007-11-14  0:02     ` David Symonds
2007-11-14  0:16       ` Kristis Makris
2007-11-14  0:27         ` David Symonds
2007-11-14  1:11           ` Junio C Hamano
2007-11-14  1:16             ` David Symonds
2007-11-14  1:27               ` Junio C Hamano
2007-11-14  1:09         ` Junio C Hamano
     [not found]           ` <7vtznppr8m.fsf-jO8aZxhGsIagbBziECNbOZn29agUkmeCHZ5vskTnxNA@public.gmane.org>
2008-08-13  9:23             ` Kristis Makris
2007-11-14  6:08     ` Martin Langhoff
2007-11-13 23:47 ` Alex Riesen
2007-11-13 23:53   ` David Symonds
2007-11-14  0:04     ` Alex Riesen
2007-11-14  0:08       ` David Symonds
2007-11-14  0:01   ` Kristis Makris

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=1194980792.4106.6.camel@localhost \
    --to=kristis.makris-ttjs1oqo2yy@public.gmane.org \
    --cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=scmbug-users-G8y9j4K4DsPiwOUmbS1EgQ@public.gmane.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).