git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git counterpart to SVN bugtraq properties?

From
Marc Strapetz <marc.strapetz@syntevo.com>
Date
Sep 30, 2013, 16:54 UTC
Message-ID
<5249ACCB.5090007@syntevo.com>
In-Reply-To
<20130717133357.GB2337@serenity.lan>
On 17.07.2013 15:33, John Keeping wrote:
Show 24 quoted lines
> 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
Previous: Marc StrapetzNext: Jonathan Nieder
Message 4 of 10 in “Git counterpart to SVN bugtraq properties?”
  1. Marc StrapetzJul 17, 2013
  2. John KeepingJul 17, 2013
  3. Marc StrapetzJul 18, 2013
  4. Marc StrapetzSep 30, 2013
  5. Jonathan NiederSep 30, 2013
  6. Marc StrapetzOct 1, 2013
  7. Thomas KochOct 4, 2013
  8. Marc StrapetzOct 4, 2013
  9. Thomas KochOct 4, 2013
  10. Marc StrapetzOct 1, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.