public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
	Arjan van de Ven <arjan@infradead.org>,
	Hua Zhong <hzhong@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] Tigran Aivazian: remove bouncing email addresses
Date: Sat, 2 Dec 2006 21:42:13 +0000	[thread overview]
Message-ID: <20061202214213.2188bced@localhost.localdomain> (raw)
In-Reply-To: <20061202213200.GZ11084@stusta.de>

On Sat, 2 Dec 2006 22:32:00 +0100 Adrian Bunk <bunk@stusta.de> wrote:

> as I explained with my email address as an example, email addresses 
> aren't suitable for this.

I disagree. They can be very useful for tracking people down, and also
for finding information as the email address (old or otherwise) is a
great search key for info on a driver in mailing lists.
 
> Even the "please contact the author" and the printk() should continue to 
> contain known bouncing addresses?

Possibly not.
 

  reply	other threads:[~2006-12-02 21:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-01  5:51 [2.6 patch] Tigran Aivazian: remove bouncing email addresses Adrian Bunk
2006-12-01  6:00 ` Hua Zhong
2006-12-01  6:19   ` Adrian Bunk
2006-12-01  6:38     ` Hua Zhong
2006-12-01  9:08   ` Arjan van de Ven
2006-12-01  9:21     ` Tigran Aivazian
2006-12-01  9:26       ` Arjan van de Ven
2006-12-01 10:59     ` Adrian Bunk
2006-12-02 21:08       ` Tigran Aivazian
2006-12-02 21:32         ` Adrian Bunk
2006-12-02 21:42           ` Alan [this message]
2006-12-02 22:07             ` grundig
2006-12-02 22:02           ` Tigran Aivazian
2006-12-01 20:33     ` Stephen Pollei
2006-12-01 21:40   ` Jesper Juhl
2006-12-02 21:33     ` Tigran Aivazian

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=20061202214213.2188bced@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=bunk@stusta.de \
    --cc=hzhong@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tigran@aivazian.fsnet.co.uk \
    /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