All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: "John Anthony Kazos Jr." <jakj@j-a-k-j.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Rusty Russell <rusty@rustcorp.com.au>,
	bunk@stusta.de, randy.dunlap@oracle.com,
	akpm@linux-foundation.org, rpjday@mindspring.com,
	marcel@holtmann.org, hch@infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] module_author: don't advice putting in an email address
Date: Fri, 11 May 2007 22:50:52 +0200	[thread overview]
Message-ID: <4644D72C.9000401@gmail.com> (raw)
In-Reply-To: <alpine.DEB.0.98.0705110740420.12363@sigma.j-a-k-j.com>

On 05/11/2007 01:42 PM, John Anthony Kazos Jr. wrote:

> 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.

Yes, that's close to Rusty's version of the original MODULE_MAINTAINER proposal:

http://lkml.org/lkml/2007/4/23/115

If I have the "ignore those other addresses you see listed here please, this 
is the contact address" method this would provide, I don't believe more 
annotations would be needed really.

Rene.


  reply	other threads:[~2007-05-11 20:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11  0:50 [PATCH] module_author: don't advice putting in an email address Rene Herman
2007-05-11 10:46 ` Alan Cox
2007-05-11 11:42   ` John Anthony Kazos Jr.
2007-05-11 20:50     ` Rene Herman [this message]
2007-05-11 21:18     ` Adrian Bunk
2007-05-11 21:35       ` Alan Cox
2007-05-12  7:14         ` Adrian Bunk
2007-05-12 12:15           ` Alan Cox
2007-05-12 12:38             ` Adrian Bunk
2007-05-11 14:16   ` Rene Herman
2007-05-11 14:40     ` Alan Cox
2007-05-11 17:21       ` Rene Herman
2007-05-11 23:23         ` Krzysztof Halasa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4644D72C.9000401@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bunk@stusta.de \
    --cc=hch@infradead.org \
    --cc=jakj@j-a-k-j.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rpjday@mindspring.com \
    --cc=rusty@rustcorp.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.