From: Marc Strapetz <marc.strapetz@syntevo.com>
To: John Keeping <john@keeping.me.uk>
Cc: git@vger.kernel.org
Subject: Re: Git counterpart to SVN bugtraq properties?
Date: Mon, 30 Sep 2013 18:54:35 +0200 [thread overview]
Message-ID: <5249ACCB.5090007@syntevo.com> (raw)
In-Reply-To: <20130717133357.GB2337@serenity.lan>
On 17.07.2013 15:33, John Keeping 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. For SVN, one can use
>> bugtraq-properties [1] to specify e.g. the issue tracker URL or how to
>> parse the bug ID from a commit message. AFAIU, there is nothing
>> comparable for Git [2]? If that's actually the case, is someone
>> interested in working out a similar specification for Git?
>>
>> [1] http://code.google.com/p/tortoisesvn/source/browse/tags/version_1.2.0/doc/issuetrackers.txt
>>
>> [2] http://stackoverflow.com/questions/17545548
>
> The Git way to record the issue ID as a footer in the commit message.
> See for example [1]. Although I'm not aware of any standard for naming
> this footer.
>
> In terms of recording the URL and other data, I think you'd want a
> dotfile in the repository (perhaps .bugzilla). This shoudld probably be
> in the gitconfig format, like .gitmodules.
>
> I think "all" it needs is to draw up a spec for the names of keys and
> format of their values, along with the format of footer(s) identifying
> issues associated with a commit and to persuade UI developers to support
> it... ;-)
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
I'd appreciate comments and pull requests.
-Marc
next prev parent reply other threads:[~2013-09-30 17:00 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 [this message]
2013-09-30 18:55 ` Jonathan Nieder
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=5249ACCB.5090007@syntevo.com \
--to=marc.strapetz@syntevo.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
/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).