git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kristis Makris <kristis.makris@asu.edu>
To: Alex Riesen <raa.lkml@gmail.com>, jnareb@gmail.com
Cc: git@vger.kernel.org, scmbug-users@lists.mkgnu.net
Subject: Re: Git and Scmbug integration
Date: Tue, 13 Nov 2007 17:01:33 -0700	[thread overview]
Message-ID: <1194998493.4106.30.camel@localhost> (raw)
In-Reply-To: <20071113234722.GK3268@steel.home>

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]

On Wed, 2007-11-14 at 00:47 +0100, Alex Riesen wrote:
> > There's no hook that will trigger when a tag is applied.
> 
> what for?

To implement the synchronous verification checks provided by Scmbug:

http://www.mkgnu.net/?q=scmbug
http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-23-0/manual/html-single/manual.html#VERIFICATION-CHECKS

In particular:

(1) Convention-based labeling

http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-23-0/manual/html-single/manual.html#VERIFICATION-CHECKS-CONVENTION-BASED-LABELING

(2) The capability to freeze access to certain branches

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

(3) Valid product-name verification

http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-23-0/manual/html-single/manual.html#VERIFICATION-CHECKS-VALID-PRODUCT-NAME


There are a lot more checks, as you can see from the manual, that are
needed on a commit trigger, rather than just a tag trigger.

A lot of people find the integration provided by Scmbug useful and some
(Jakub, back me up here) have requested support for Git.



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

      parent reply	other threads:[~2007-11-14  0:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 19:06 Git and Scmbug integration Kristis Makris
2007-11-13 23:00 ` 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 [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=1194998493.4106.30.camel@localhost \
    --to=kristis.makris@asu.edu \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=raa.lkml@gmail.com \
    --cc=scmbug-users@lists.mkgnu.net \
    /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).