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:39:13
Message-Id: 55C76603.7020109@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:26 PM, Dirkjan Ochtman wrote:
2 > On Sun, Aug 9, 2015 at 4:09 PM, hasufell <hasufell@g.o> wrote:
3 >> I was wondering if we should set a standard for referencing bug reports.
4 >> The portage team already does something like that:
5 >> https://github.com/gentoo/portage/commit/b7149002bf23889f280c502afe6ceda0b1345ca3
6 >>
7 >> Following that, the commit could have been:
8 >> =====
9 >> sci-libs/opencascade: add USE=vtk
10 >>
11 >> thanks to Helmut Jarausch
12 >>
13 >> X-Gentoo-Bug: 557022
14 >> X-Gentoo-Bug-url: https://bugs.gentoo.org/show_bug.cgi?id=557022
15 >> =====
16 >
17 > I don't really see why it has to be so verbose. Can we just make it
18 > "bug 557022", or even #557022? That would also make it fit better if
19 > you have a single-line commit message only.
20 >
21
22 I think "X-Gentoo-Bug: 557022" also makes the job easier for tools that
23 parse commit messages.

Replies