[lkml]   [2012]   [Jan]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] fs: Fix mod_timer crash when removing USB sticks
    On Thu, Jan 12, 2012 at 4:53 PM, Mandeep Singh Baines <> wrote:
    > What is the conventional way of doing this? There is a lot of good
    > data in the bug report which might be useful to reviewers. We
    > couldn't find a de-facto way of referencing the downstream bug database
    > so we just made up a new field. Sorry. We'll use the correct
    > field name next time.

    There isn't a "correct field name", since it hasn't been standardized.
    I can tell you as an the ext4 maintainer, I've put things like:

    Addresses-Redhat-Bugzilla: <Bugzilla #>


    Addresses-Debian-Bug: <debian-bug-number>

    etc. in commit messages. I usually put them before the signed-off-block,
    i.e, like this:

    ext4: a simple commit

    This is the longer commit description, blah, blah, blah.

    Addresses-Redhat-Bugzilla: 12345

    Signed-off-by: Eric Sandeen <>
    Signed-off-by: Theodore Ts'o <>

    There is some disagreement about whether it's useful to do this
    for bugzilla entries which are not publically available (i.e., protected
    Enterprise Linux bugzillas which have customer information and
    thus are restricted access, or internal Company bug numbers).

    My personal take on this matter is that if an engineer from a
    particular company has taken the time and effort to contribute
    a bug that fixes a bug that they had seen internally, and they
    include an internal bug number, it's presumably to make it easier
    to track when a particular commit fixing a bug that they really
    care about has hit upstream. It costs me very little to keep
    the bug tracker reference, even if I don't have personal access
    to it, and given the code contributor has helped me by submitting
    a bug fix, it's nice to be able to do a little something nice in
    return. The extra line doesn't really bloat the "git log" output
    by all that much.

    Others, including Greg K-H, think it's a horrible thing to do,
    and will reject commits on that basis.

    So it all depends on which subsystem maintainer handles
    your bug..... at the end, it's up to the maintainer. I've never
    had Linus complain to me because the commits that I ask him
    to pull might include "Google-Bug-Id: 12345" lines in the commit

    -- Ted

     \ /
      Last update: 2012-01-12 23:15    [W:0.023 / U:26.276 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site