From: Adrian Bunk <bunk@stusta.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Hua Zhong <hzhong@gmail.com>,
tigran@aivazian.fsnet.co.uk, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] Tigran Aivazian: remove bouncing email addresses
Date: Fri, 1 Dec 2006 11:59:55 +0100 [thread overview]
Message-ID: <20061201105955.GO11084@stusta.de> (raw)
In-Reply-To: <1164964119.3233.56.camel@laptopd505.fenrus.org>
On Fri, Dec 01, 2006 at 10:08:39AM +0100, Arjan van de Ven wrote:
> On Thu, 2006-11-30 at 22:00 -0800, Hua Zhong wrote:
> > I am curious, what's the point?
> >
> > These email addresses serve a "historical" purpose: they tell when the contribution was made, what the author's email addresses
> > were at that point.
>
>
> .. and which company owns the copyright.
>...
Email addresses aren't good for this kind of information.
As an example, what is stusta.de and does it have any rights on my
contributions? [1]
cu
Adrian
[1] it can't own the copyright since in Germany the copyright belongs
untransferably [2] to the author [3]
[2] except for heritage
[3] but he can give exclusive usage rights for known kinds of usage
--
"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
next prev parent reply other threads:[~2006-12-01 10:59 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 [this message]
2006-12-02 21:08 ` Tigran Aivazian
2006-12-02 21:32 ` Adrian Bunk
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=20061201105955.GO11084@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.