From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, TeLeMan <geleman@gmail.com>,
"Andreas Färber" <afaerber@suse.de>,
"Avi Kivity" <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] exec: fix breakpoint_invalidate() breakage
Date: Wed, 23 May 2012 15:44:31 -0500 [thread overview]
Message-ID: <4FBD4C2F.5080606@codemonkey.ws> (raw)
In-Reply-To: <CAAu8pHs2jYANAcEbT-MvRShKXw=ha4y4B=UJbKrve+MdA9VzKw@mail.gmail.com>
On 05/23/2012 03:28 PM, Blue Swirl wrote:
> On Wed, May 23, 2012 at 8:04 PM, Andreas Färber<afaerber@suse.de> wrote:
>> Am 23.05.2012 21:40, schrieb Blue Swirl:
>>> On Wed, May 23, 2012 at 3:41 AM, Andreas Färber<afaerber@suse.de> wrote:
>>>> Am 18.05.2012 11:49, schrieb TeLeMan:
>>>>> This breakage was introduced by the commit "memory: make
>>>>> phys_page_find() return an unadjusted".
>>>>
>>>> You seem to have found the origin of your problem. If you also mention
>>>> the commit hash in your commit message then certain frontends (gitk,
>>>> repo.or.cz) will display it as a handy hyperlink to that commit.
>>>>
>>>>>
>>>>> Signed-off-by: TeLeMan<geleman@gmail.com>
>>>>
>>>> Signed-off-by is a legal statement of origin and must not be a pseudonym.
>>>
>>> $ git log --author=.*eleman
>>> commit c62f6d1d76aea587556c85b6b7b5c44167006264
>>> Author: TeLeMan<geleman@gmail.com>
>>> Date: Mon Jul 25 16:29:14 2011 +0800
>>>
>>> monitor: fix build breakage with --disable-vnc
>>>
>>> The breakage was introduced by the commit
>>> 13661089810d3e59931f3e80d7cb541b99af7071
>>>
>>> Signed-off-by: TeLeMan<geleman@gmail.com>
>>> Signed-off-by: Anthony Liguori<aliguori@us.ibm.com>
>>>
>>> and several others.
>>
>> Funny, since I learned that from Anthony. :-)
Signed-off-by is a contractual statement and your real name is required:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches#l339
But I'm generally going to assume that if you SoB something, it's your real
name. I have challenged people in the past but only when it's very obviously
fake. If TeLeMan is not your real name, you cannot Signed-off-by with it.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2012-05-23 20:44 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 [this message]
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
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=4FBD4C2F.5080606@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 \
/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).