lkml.org 
[lkml]   [2007]   [Aug]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
    > MODULE_MAINTAINER() was discussed a while ago but embedding information into 
    > the binary has the problem you can't ever change deployed systems, meaning
    > it lags by design. If a maintainer changes, people would still be using the
    > information from their old binaries, meaning a replaced maintainer might get
    > contacted for potentially years still (and the new one not).

    And as was pointed out at the time, the people whining about that were
    talking out of the wrong equipment. The supplier of the code can no more
    or less easily change the binary as the matching source tree once its been
    shipped. In fact its probably easier to change the binaries as the
    sources will be left on CD.

    The only non-stale source is git-blame.

    Alan
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-08-14 11:17    [W:4.031 / U:0.064 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site