From: Krzysztof Halasa <khc@pm.waw.pl>
To: Rene Herman <rene.herman@gmail.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: Sat, 12 May 2007 01:23:27 +0200 [thread overview]
Message-ID: <m3hcqj6j2o.fsf@maximus.localdomain> (raw)
In-Reply-To: <4644A637.1060507@gmail.com> (Rene Herman's message of "Fri, 11 May 2007 19:21:59 +0200")
Rene Herman <rene.herman@gmail.com> writes:
> /* Author, ideally of form NAME <EMAIL>[, NAME <EMAIL>]*[ and NAME <EMAIL>]
>
> After my trivial patch, it says:
>
> /* Author, ideally of form NAME[, NAME]*[ and NAME] */
I think I would put something like this:
/* Author, of form NAME[, NAME]*[ and NAME]
* If you have a permanent email address and are prepared for
maintaining/supporting the module, you may want to provide
the address as well */
The wording isn't the best I suppose.
I.e., the change would mean providing the address is not strictly
required and the person should think when adding it, that's all.
--
Krzysztof Halasa
prev parent reply other threads:[~2007-05-11 23:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 0:50 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
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 [this message]
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=m3hcqj6j2o.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=randy.dunlap@oracle.com \
--cc=rene.herman@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®