From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefan Weil <sw@weilnetz.de>
Cc: "Blue Swirl" <blauwirbel@gmail.com>, TeLeMan <geleman@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
"Avi Kivity" <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] exec: fix breakpoint_invalidate() breakage
Date: Thu, 24 May 2012 13:36:06 -0500 [thread overview]
Message-ID: <4FBE7F96.3010405@codemonkey.ws> (raw)
In-Reply-To: <4FBE7A0C.3060707@weilnetz.de>
On 05/24/2012 01:12 PM, Stefan Weil wrote:
> Am 24.05.2012 15:35, schrieb Andreas Färber:
>> Am 24.05.2012 04:12, schrieb TeLeMan:
>>> I won't use
>>> my Chinese name because I think it's my privacy.
>>
>> That exactly is touching the core point: Signed-off-by is about
>> transparency and taking responsibility for your actions, not hiding in
>> anonymity. It's a certification of whom the code came from and who would
>> be to blame if anything was wrong with that (think non-GPL-compatible
>> code taken from somewhere else).
>>
>> Why should you be granted more privacy than us just because your name is
>> Chinese? There's quite a few Chinese IBM guys around that don't seem to
>> have any problem with this, and git would even handle UTF-8 characters
>> quite well if desired[*].
>>
>> Andreas
>>
>>
>> [*] For example,
>>
>> commit e965fc380703110e967febf8d5b2ecd7db53b5d2
>> Author: 陳韋任<chenwj@iis.sinica.edu.tw>
>> Date: Mon Feb 6 14:02:55 2012 +0800
>>
>> cpu-exec.c: Correct comment about this file and indentation cleanup
>>
>> Each target uses the #define macro (in target-xxx/cpu.h) to rename
>> cpu_exec (cpu-exec.c) to cpu_xxx_exec, then defines its own cpu_loop
>> which calls cpu_xxx_exec. So basically, cpu-exec.c is not only the i386
>> emulator main execution loop. This patch corrects the comment of this
>> file and does indentation cleanup.
>>
>> Signed-off-by: Chen Wei-Ren (陳韋任)<chenwj@iis.sinica.edu.tw>
>> Signed-off-by: Stefan Hajnoczi<stefanha@linux.vnet.ibm.com>
>
> 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
next prev parent reply other threads:[~2012-05-24 18:36 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 [this message]
2012-05-24 19:42 ` Stefan Weil
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=4FBE7F96.3010405@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=afaerber@suse.de \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=geleman@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).