From: "Andreas Färber" <afaerber@suse.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: TeLeMan <geleman@gmail.com>, Avi Kivity <avi@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] exec: fix breakpoint_invalidate() breakage
Date: Wed, 23 May 2012 22:04:41 +0200 [thread overview]
Message-ID: <4FBD42D9.6050809@suse.de> (raw)
In-Reply-To: <CAAu8pHtrQAKDXshN7FdNdMz0NZhm0D9Z23unoXS9EW0tNNxcKw@mail.gmail.com>
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. :-)
Anyway, the only non-childish reason to contribute under a pseudonym (as
opposed to a known alias*) I can imagine is a contribution from someone
working on a competing commercial emulation/virtualization solution who
doesn't want her employer finding out, in which case it is questionable
whether she can actually sign off her own code as it may conflict with
non-free company IP. Any comments, Mr. Blauwirbel? ;)
Andreas
* e.g., malc, kraxel, mmu_man
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-05-23 20:05 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 [this message]
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
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=4FBD42D9.6050809@suse.de \
--to=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).