From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/)
Date: Sun, 9 Aug 2015 11:43:18 -0400 [thread overview]
Message-ID: <CAJ0EP43DoOTFvDDvb+npr23t_NWguqOk8fJvK9bni3YptzaTVQ@mail.gmail.com> (raw)
In-Reply-To: <55C77214.107@gentoo.org>
On Sun, Aug 9, 2015 at 11:30 AM, hasufell <hasufell@gentoo.org> wrote:
> On 08/09/2015 05:19 PM, Tobias Klausmann wrote:
>> Hi!
>>
>> On Sun, 09 Aug 2015, Sven Vermeulen wrote:
>>
>>> On Sun, Aug 09, 2015 at 04:43:36PM +0200, Dirkjan Ochtman wrote:
>>>>> I think "X-Gentoo-Bug: 557022" also makes the job easier for tools that
>>>>> parse commit messages.
>>>>
>>>> I don't. Just the "bug " prefix should be fine for almost all
>>>> purposes, even for tools.
>>>
>>> I'm pretty sure the majority of developers don't care that one developer
>>> uses "X-Gentoo-Bug" and another just adds it to the commit title.
>>>
>>> I like /guidelines/ in the sense that, if I don't know something, I can look
>>> it up. But don't make it mandatory until we start depending on it (for
>>> instance, when we would automate stuff based on the content of the commit
>>> message).
>>
>> I'd just go with "Gentoo-Bug". The X- is pointless since it was
>> for eXtending Email-Headers. And what we do is only linked in
>> style.
>>
>
> I'd be fine with that and add a reference to the kernel guideline [0] to
> the wiki as well, so that it is clear that we also allow/use Acked-by,
> Reviewed-by, Suggested-by and whatnot.
>
> I'll wait for more ++ though.
I like Gentoo-Bug. Much nicer without the X-.
next prev parent reply other threads:[~2015-08-09 15:43 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1439128706.40b3fd64ec9c5d6d94f0f0897740bc77622c24a1.xmw@gentoo>
2015-08-09 14:09 ` [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/) hasufell
2015-08-09 14:18 ` Ian Whyman
2015-08-09 14:26 ` Dirkjan Ochtman
2015-08-09 14:38 ` hasufell
2015-08-09 14:43 ` Dirkjan Ochtman
2015-08-09 14:47 ` hasufell
2015-08-09 14:54 ` Michael Orlitzky
2015-08-09 15:03 ` Sven Vermeulen
2015-08-09 15:06 ` hasufell
2015-08-09 15:19 ` Tobias Klausmann
2015-08-09 15:30 ` hasufell
2015-08-09 15:43 ` Mike Gilbert [this message]
2015-08-09 18:49 ` Davide Pesavento
2015-08-09 23:58 ` Daniel Campbell (zlg)
2015-08-10 0:25 ` Alexandre Rostovtsev
2015-08-09 19:56 ` Michał Górny
2015-08-09 21:01 ` hasufell
2015-08-09 21:11 ` Michał Górny
2015-08-09 21:30 ` Rich Freeman
2015-08-10 0:02 ` Daniel Campbell (zlg)
2015-08-10 7:31 ` Andrew Savchenko
2015-08-09 21:44 ` Andrew Savchenko
2015-08-09 22:40 ` Michał Górny
2015-08-09 23:16 ` Andrew Savchenko
2015-08-09 23:46 ` hasufell
2015-08-10 0:05 ` Daniel Campbell (zlg)
2015-08-10 0:10 ` Kent Fredric
2015-08-10 0:51 ` [gentoo-dev] Referencing bug reports in git Ulrich Mueller
2015-08-10 1:02 ` hasufell
2015-08-10 4:29 ` [gentoo-dev] " Ryan Hill
2015-08-10 12:25 ` Duncan
2015-08-10 22:57 ` Gordon Pettey
2015-08-11 1:03 ` Duncan
2015-08-11 0:17 ` Ryan Hill
2015-08-11 1:25 ` Duncan
2015-08-11 8:57 ` Tobias Klausmann
2015-08-11 9:12 ` Kent Fredric
2015-08-11 11:49 ` Rich Freeman
2015-08-11 11:58 ` hasufell
2015-08-12 7:20 ` [gentoo-dev] Bisecting Was: " Duncan
2015-08-12 7:38 ` Jason Zaman
2015-08-12 8:42 ` [gentoo-dev] " Duncan
2015-08-11 14:28 ` [gentoo-dev] Summary line (was: Re: Referencing bug reports in git) Ian Stakenvicius
2015-08-11 14:35 ` Kent Fredric
2015-08-11 15:27 ` [gentoo-dev] Summary line Ian Stakenvicius
2015-08-31 14:53 ` [gentoo-dev] Summary line (was: Re: Referencing bug reports in git) Alec Warner
2015-08-31 17:33 ` Rich Freeman
2015-08-31 18:16 ` [gentoo-dev] Summary line Michael Orlitzky
2015-08-11 14:36 ` hasufell
2015-08-11 14:39 ` Mikle Kolyada
2015-08-10 9:45 ` [gentoo-dev] Referencing bug reports in git Chí-Thanh Christopher Nguyễn
2015-08-10 10:16 ` Ulrich Mueller
2015-08-10 13:19 ` Michał Górny
2015-08-10 14:42 ` hasufell
2015-08-10 18:44 ` Chí-Thanh Christopher Nguyễn
2015-08-10 13:11 ` [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/) Michał Górny
2015-08-10 20:43 ` Andrew Savchenko
2015-08-10 21:06 ` Michał Górny
2015-08-11 6:56 ` Dmitry Yu Okunev
2015-08-11 7:12 ` Michał Górny
2015-08-11 8:34 ` Dmitry Yu Okunev
2015-08-11 0:52 ` [gentoo-dev] " Ryan Hill
2015-08-10 0:08 ` Ryan Hill
2015-08-12 10:40 ` [gentoo-dev] Re: Referencing bug reports in git hasufell
2015-08-12 15:59 ` Chí-Thanh Christopher Nguyễn
2015-08-12 16:03 ` Michał Górny
2015-08-12 16:25 ` Chí-Thanh Christopher Nguyễn
2015-08-12 16:34 ` Michał Górny
2015-08-12 16:39 ` Ian Stakenvicius
2015-08-13 5:48 ` Ryan Hill
2015-08-13 11:19 ` Ben de Groot
2015-08-13 12:13 ` Rich Freeman
2015-08-14 13:37 ` Aaron W. Swenson
2015-08-18 6:03 ` Ryan Hill
2015-08-14 20:04 ` Andrew Savchenko
2015-08-14 20:17 ` Matthias Maier
2015-08-15 7:17 ` Daniel Campbell (zlg)
2015-08-12 16:15 ` hasufell
2015-08-12 17:38 ` Matt Turner
2015-08-12 17:48 ` Dmitry Yu Okunev
2015-08-12 17:54 ` hasufell
2015-08-13 2:30 ` [gentoo-dev] " Steev Klimaszewski
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=CAJ0EP43DoOTFvDDvb+npr23t_NWguqOk8fJvK9bni3YptzaTVQ@mail.gmail.com \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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