Gentoo Archives: gentoo-dev

From: hasufell <hasufell@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/)
Date: Sun, 09 Aug 2015 14:47:54
Message-Id: 55C76805.9050601@gentoo.org
In Reply to: Re: [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/) by Dirkjan Ochtman
1 On 08/09/2015 04:43 PM, Dirkjan Ochtman wrote:
2 > On Sun, Aug 9, 2015 at 4:38 PM, hasufell <hasufell@g.o> wrote:
3 >>> I don't really see why it has to be so verbose. Can we just make it
4 >>> "bug 557022", or even #557022? That would also make it fit better if
5 >>> you have a single-line commit message only.
6 >>
7 >> I think "X-Gentoo-Bug: 557022" also makes the job easier for tools that
8 >> parse commit messages.
9 >
10 > I don't. Just the "bug " prefix should be fine for almost all
11 > purposes, even for tools.
12 >
13 > Also, https://tools.ietf.org/html/rfc6648.
14 >
15
16 That can be ambiguous, because it isn't clear whether you are
17 referencing a gentoo bug. You can reference bugs from other bugtrackers
18 as well.