From: Jonathan Nieder <jrnieder@gmail.com>
To: Marc Strapetz <marc.strapetz@syntevo.com>
Cc: John Keeping <john@keeping.me.uk>, git@vger.kernel.org
Subject: Re: Git counterpart to SVN bugtraq properties?
Date: Mon, 30 Sep 2013 11:55:13 -0700 [thread overview]
Message-ID: <20130930185513.GS9464@google.com> (raw)
In-Reply-To: <5249ACCB.5090007@syntevo.com>
Hi,
Marc Strapetz wrote:
>> On Wed, Jul 17, 2013 at 03:03:14PM +0200, Marc Strapetz wrote:
>>> I'm looking for a specification or guidelines on how a Git client should
>>> integrate with bug tracking systems.
[...]
> Finally, I've created a minimal spec which is sufficient to parse and
> display issue IDs:
>
> https://github.com/mstrap/bugtraq/blob/master/specification.txt
Neat. :)
It reminds me a little of Gerrit's commentlink functionality, though
that tries to solve a different / more generic problem (automatic
linking in commit messages in general, not just to bug trackers):
https://gerrit-review.googlesource.com/Documentation/config-gerrit.html#_a_id_commentlink_a_section_commentlink
Some projects use more than one bug tracker. For example, a distro
might have its own bug tracking system and also sometimes make commits
that refer to the upstream bug tracker. I don't think that's
important to necessarily address in the first version of a project
like this, but thought I should mention it to help plans for the
future.
Gerrit keeps its configuration in a file named "project.config" in the
tree associated to the refs/meta/config commit so a single
configuration can be applied to the entire repository. Which
.gitbugtraq file should take effect in a repository with multiple
branches?
Hope that helps,
Jonathan
next prev parent reply other threads:[~2013-09-30 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 13:03 Git counterpart to SVN bugtraq properties? Marc Strapetz
2013-07-17 13:33 ` John Keeping
2013-07-18 13:32 ` Marc Strapetz
2013-09-30 16:54 ` Marc Strapetz
2013-09-30 18:55 ` Jonathan Nieder [this message]
2013-10-01 11:58 ` Marc Strapetz
[not found] ` <CACXt3y82u3KtR7cq5Kyb1PDi1aq7095uO2-eGQTLq0yDuNZ73Q@mail.gmail.com>
2013-10-01 12:24 ` Marc Strapetz
2013-10-04 9:15 ` Thomas Koch
2013-10-04 11:22 ` Marc Strapetz
2013-10-04 12:36 ` Thomas Koch
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=20130930185513.GS9464@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=marc.strapetz@syntevo.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.