[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.0.98.0705110740420.12363@sigma.j-a-k-j.com>
Date: Fri, 11 May 2007 07:42:38 -0400 (EDT)
From: "John Anthony Kazos Jr." <jakj@...-k-j.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
cc: Rene Herman <rene.herman@...il.com>,
Rusty Russell <rusty@...tcorp.com.au>, bunk@...sta.de,
randy.dunlap@...cle.com, akpm@...ux-foundation.org,
rpjday@...dspring.com, marcel@...tmann.org, hch@...radead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] module_author: don't advice putting in an email
address
> > 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists