From: Thomas Koch <thomas@koch.ro>
To: Marc Strapetz <marc.strapetz@syntevo.com>
Cc: git@vger.kernel.org
Subject: Re: Git counterpart to SVN bugtraq properties?
Date: Fri, 4 Oct 2013 14:36:41 +0200 [thread overview]
Message-ID: <201310041436.41644.thomas@koch.ro> (raw)
In-Reply-To: <524EA4E0.5000605@syntevo.com>
On Friday, October 04, 2013 01:22:08 PM Marc Strapetz wrote:
> On 04.10.2013 11:15, Thomas Koch wrote:
> > On Wednesday, July 17, 2013 03:03:14 PM 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 ...
> >
> > There's seldom a question that has not been asked before. There already
> > is a popular standard for project information like the link to a
> > bugtracker and much more: https://en.wikipedia.org/wiki/DOAP
> > (Description of a Project)
>
> I can't see how that relates to concepts like (SVN) bugtraq properties.
You asked for a place to write the bugtracker URL to. DOAP defines a data
structure that also contains the bugtracker URL of a project. Just place a
doap file in your Git repo and parse it.
Regards, Thomas Koch
prev parent reply other threads:[~2013-10-04 12:36 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
2013-10-04 9:15 ` Thomas Koch
2013-10-04 11:22 ` Marc Strapetz
2013-10-04 12:36 ` Thomas Koch [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=201310041436.41644.thomas@koch.ro \
--to=thomas@koch.ro \
--cc=git@vger.kernel.org \
--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.