On 02/06/2018 03:36 PM, Ulrich Mueller wrote: >>>>>> On Tue, 6 Feb 2018, Kristian Fiskerstrand wrote:
>> More generally though, should we start requiring more verbose commit >> messages for eclasses to make it easier to trace changes in our git >> repo directly without reaching out to bugs? At least including >> summaries of the respective bugs as a short description? > > In the concrete example, the bug's summary is "bzr.eclass might need > to use bzr pull's --overwrite-tags flag" which is not much different > from the git commit message. Right, this specific commit likely has little more to gain given the summary line. But could easily benefit from some text in body still :) But I generally think we can benefit from some more verbosity in our commit messages, in particular for eclasses. -- Kristian Fiskerstrand OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
