| 1 |
On 08/09/2015 10:43 AM, 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 |
There's a "standard" set of patch tags all in the style of RFC822 |
| 17 |
headers -- Signed-off-by, Acked-by, Suggested-by, etc. are all common: |
| 18 |
|
| 19 |
https://www.kernel.org/doc/Documentation/SubmittingPatches |
| 20 |
|
| 21 |
X-Gentoo-Bug is just following that example for metadata. |
Archives