lkml.org 
[lkml]   [2007]   [May]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] module_author: don't advice putting in an email address
    On Fri, May 11, 2007 at 07:42:38AM -0400, John Anthony Kazos Jr. wrote:
    > > > The email address is the problem I was trying to fix; with multiple current
    > > > and non-current authors and maintainers who might not even be authors the
    > > > address(es) available from the tag confuse the issue of whom to contact.
    > > > It's moreover also information that easily outdated.
    > > >
    > > > A bit more than half of the tags in the tree don't include an email address
    > > > already and I'll submit patches removing more...
    > >
    > > Please don't do this
    > >
    > > NACK this change.
    > >
    > > Whether someone puts their email address into the entry is their own
    > > business. We do not need a style police for module author entries.
    > >
    > > At most you might want to put
    > >
    > > "If you include an email address then please use an address that
    > > you expect to keep for the long term, and if you change address
    > > please remember to update or remove the entry"
    > >
    > > > A bit more than half of the tags in the tree don't include an email
    > > > address already and I'll submit patches removing more...
    > >
    > > And I'll NAK every one which hasn't been signed off by the email address
    > > listed OR the address bounces. In which case removing it is good.
    >
    > Can't we just subtitle it somehow? Add tags: " (current maintainer)",
    > " (original author, inactive)", " (bug and defect reports)", or whatever
    > you like after the names.

    This still wouldn't solve the following problems:
    - I doubt it will be kept up to date for all > 2800 modules in the kernel
    - the 3 year old kernel of your distribution would contain 3 year old
    maintainership information
    - maintainers sometimes disappear

    The default for "bug and defect reports" should be for all modules (as
    well as for non-modular code) from ftp.kernel.org kernels either
    linux-kernel or the kernel Bugzilla. [1]

    For distribution kernels (which are what most users are using), the
    default for "bug and defect reports" should be the distribution support.

    cu
    Adrian

    [1] contacting the maintainer directly is often better, but there's no
    sane way to put this information into the kernel binary

    --

    "Is there not promise of rain?" Ling Tan asked suddenly out
    of the darkness. There had been need of rain for many days.
    "Only a promise," Lao Er said.
    Pearl S. Buck - Dragon Seed

    -
    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-05-11 23:21    [W:0.021 / U:126.036 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site