| 1 |
>>>>> On Tue, 6 Feb 2018, Kristian Fiskerstrand wrote: |
| 2 |
|
| 3 |
>> Fixes: https://bugs.gentoo.org/446422 |
| 4 |
|
| 5 |
> Bug or Closes, Fixes would be referencing a commit-id c.f GLEP 66. |
| 6 |
|
| 7 |
Updated, thanks for catching this. |
| 8 |
|
| 9 |
> More generally though, should we start requiring more verbose commit |
| 10 |
> messages for eclasses to make it easier to trace changes in our git |
| 11 |
> repo directly without reaching out to bugs? At least including |
| 12 |
> summaries of the respective bugs as a short description? |
| 13 |
|
| 14 |
In the concrete example, the bug's summary is "bzr.eclass might need |
| 15 |
to use bzr pull's --overwrite-tags flag" which is not much different |
| 16 |
from the git commit message. |
| 17 |
|
| 18 |
Ulrich |
Archives