From: Marc Strapetz <marc.strapetz@syntevo.com>
To: James Sharpe <mail@jsharpe.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
John Keeping <john@keeping.me.uk>,
git@vger.kernel.org
Subject: Re: Git counterpart to SVN bugtraq properties?
Date: Tue, 01 Oct 2013 14:24:18 +0200 [thread overview]
Message-ID: <524ABEF2.1060008@syntevo.com> (raw)
In-Reply-To: <CACXt3y82u3KtR7cq5Kyb1PDi1aq7095uO2-eGQTLq0yDuNZ73Q@mail.gmail.com>
On 30.09.2013 21:42, James Sharpe wrote:
> You could also use git notes to store the information. The advantage
> there is they can be added to commits without changing the history.
> Gerrit and jenkins can auto generate this sort of metadata via plugins.
git notes could be the preferred storage for issues IDs when the client
wants to add this kind of meta information on Commit. This would
actually solve one weak point of SVN bugtraq properties where you can
just specify to prepend or append an issue ID to the commit message
(i.e. silently altering the commit message).
-Marc
>
> On 30 Sep 2013 20:02, "Jonathan Nieder" <jrnieder@gmail.com
> <mailto:jrnieder@gmail.com>> wrote:
>
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> <mailto:majordomo@vger.kernel.org>
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-10-01 12:24 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
2013-10-01 11:58 ` Marc Strapetz
[not found] ` <CACXt3y82u3KtR7cq5Kyb1PDi1aq7095uO2-eGQTLq0yDuNZ73Q@mail.gmail.com>
2013-10-01 12:24 ` Marc Strapetz [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=524ABEF2.1060008@syntevo.com \
--to=marc.strapetz@syntevo.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=jrnieder@gmail.com \
--cc=mail@jsharpe.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).