All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Tigran Aivazian <tigran@aivazian.fsnet.co.uk>
Cc: 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 22:32:00 +0100	[thread overview]
Message-ID: <20061202213200.GZ11084@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0612022101500.1388@ginsburg.homenet>

On Sat, Dec 02, 2006 at 09:08:56PM +0000, Tigran Aivazian wrote:

> Hi Adrian,

Hi Tigran,

> I have only now had time to read your patch and reject most of it --- the 
> email addresses in the revision histories etc are for historical purposes 
> and as such are very useful. They are NOT meant to be valid except at the 
> moment of time when they are written. The only purpose of email address in 
> the revision history is the indication where the person worked _at the 
> time_.

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

> The only bits that should be made sure to remain valid are the 
> MODULE_AUTHOR, as Arjan also mentioned.

Even the "please contact the author" and the printk() should continue to 
contain known bouncing addresses?

> Also, it is very strange that I have _not_ received your original email 
> containing the patch --- I only saw it now via lkml archive.

I haven't yet gotten a bounce from tigran@aivazian.fsnet.co.uk.

Do you have a spamfilter?
Or a provider doing some kind of email filtering?

> Kind regards
> Tigran

cu
Adrian

-- 

       "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


  reply	other threads:[~2006-12-02 21:31 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 [this message]
2006-12-02 21:42           ` Alan
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=20061202213200.GZ11084@stusta.de \
    --to=bunk@stusta.de \
    --cc=arjan@infradead.org \
    --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 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.