Archives
Archives
| From: | Sven Vermeulen <swift@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 15:03:33 | ||
| Message-Id: | 20150809150325.GA7408@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 Sun, Aug 09, 2015 at 04:43:36PM +0200, Dirkjan Ochtman wrote: |
| 2 | > > I think "X-Gentoo-Bug: 557022" also makes the job easier for tools that |
| 3 | > > parse commit messages. |
| 4 | > |
| 5 | > I don't. Just the "bug " prefix should be fine for almost all |
| 6 | > purposes, even for tools. |
| 7 | |
| 8 | I'm pretty sure the majority of developers don't care that one developer |
| 9 | uses "X-Gentoo-Bug" and another just adds it to the commit title. |
| 10 | |
| 11 | I like /guidelines/ in the sense that, if I don't know something, I can look |
| 12 | it up. But don't make it mandatory until we start depending on it (for |
| 13 | instance, when we would automate stuff based on the content of the commit |
| 14 | message). |
| 15 | |
| 16 | Wkr, |
| 17 | Sven Vermeulen |
| Subject | Author |
|---|---|
| Re: [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/) | hasufell <hasufell@g.o> |
| Re: [gentoo-dev] Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/) | Tobias Klausmann <klausman@g.o> |