qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Blue Swirl" <blauwirbel@gmail.com>, TeLeMan <geleman@gmail.com>,
	"Avi Kivity" <avi@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] exec: fix breakpoint_invalidate() breakage
Date: Thu, 24 May 2012 21:42:17 +0200	[thread overview]
Message-ID: <4FBE8F19.3030707@weilnetz.de> (raw)
In-Reply-To: <4FBE7F96.3010405@codemonkey.ws>

Am 24.05.2012 20:36, schrieb Anthony Liguori:
> On 05/24/2012 01:12 PM, Stefan Weil wrote:
>> This discussion looks strange for me.
>
> I'm not going to commit patches with a Signed-off-by if I know the 
> name is an alias.
>
> DCO requires the use of a real name.  DCO is an important part of 
> ensuring the pedigree of a code base just like copyright licensing.
>
> Regards,
>
> Anthony Liguori
>

As I wrote in my previous mail, (personal) names are not absolute,
but influenced by cultural facts. DCO was something written by
lawyers from the western culture where individual personal names
exist since some time and where these names are usually
more or less constant during the life of a person. AFAIK,
DCO was introduced for legal reasons (SCO => DCO).

It would be interesting to know how many names used in Linux
commits since DCO are faked real names. Without enforcing
certified signatures, enforcing "real names" (that's names which
look like some name you know) does not really ensure something.
Nor does the requirement of a valid mail address.
It is only an alibi pedigree.

Even in America and Europe, the concept of a "real name" is
rather new (only some hundred years old), and there still exist cultures
without personal names. See http://en.wikipedia.org/wiki/Personal_name
for more information. People change their name even today when
they migrate from one country to another (many US immigrants did
this, too) or when they change their religion (remember Cassius Clay?).

Nevertheless I can understand that you are bound by the requirements
of your employer.

Regards,

Steve (that's the name by which I was called when I was a youngster)

  reply	other threads:[~2012-05-24 19:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18  9:49 [Qemu-devel] [PATCH] exec: fix breakpoint_invalidate() breakage TeLeMan
2012-05-22 22:54 ` TeLeMan
2012-05-23  3:41 ` Andreas Färber
2012-05-23  7:09   ` TeLeMan
2012-05-23 11:22     ` Jan Kiszka
2012-05-23 14:11       ` TeLeMan
2012-05-23 16:02         ` Jan Kiszka
2012-05-23 17:36           ` Jan Kiszka
2012-05-24  1:29             ` TeLeMan
2012-05-24  2:00               ` Jan Kiszka
2012-05-24  2:16                 ` TeLeMan
2012-05-24  2:21                 ` Jan Kiszka
2012-05-23 19:40   ` Blue Swirl
2012-05-23 20:04     ` Andreas Färber
2012-05-23 20:28       ` Blue Swirl
2012-05-23 20:44         ` Anthony Liguori
2012-05-24  2:12           ` TeLeMan
2012-05-24 13:35             ` Andreas Färber
2012-05-24 18:12               ` Stefan Weil
2012-05-24 18:36                 ` Anthony Liguori
2012-05-24 19:42                   ` Stefan Weil [this message]
2012-05-24 19:51                     ` Anthony Liguori
2012-05-25  0:43                       ` TeLeMan

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=4FBE8F19.3030707@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=geleman@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).