From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michal Prívozník" <mprivozn@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org
Cc: mtosatti@redhat.com, Sergio Lopez <slp@redhat.com>
Subject: Re: [PATCH] x86: Check for machine state object class before typecasting it
Date: Tue, 7 Jan 2020 11:27:21 +0100 [thread overview]
Message-ID: <e7b0685b-2444-d7f6-c4ba-2632bd2e4a23@redhat.com> (raw)
In-Reply-To: <337056f8-4c8f-9a18-5f58-13dc459f6346@redhat.com>
On 30/12/19 14:17, Michal Prívozník wrote:
> On 12/30/19 10:45 AM, Philippe Mathieu-Daudé wrote:
>> On 12/30/19 10:35 AM, Michal Prívozník wrote:
>>> On 12/30/19 9:41 AM, Philippe Mathieu-Daudé wrote:
>>>> On 12/30/19 9:00 AM, Michal Privoznik wrote:
>>>>> In v4.2.0-246-ged9e923c3c the SMM property was moved from PC
>>>>
>>>> Typo v4.2.0-246-ged9e923c3c -> ed9e923c3c.
>>>
>>> This depends on how you format the hash :-)
>>> I've used 'git describe ed9e923c3c' because I find it more readable for
>>> us humans (at least we see what version the commit was introduced in).
>>> But I don't know what the praxis is in qemu.
>>
>> Hmm I never used it. Your explanation makes sense, but the tag confused
>> me because I don't have it locally. However git (and gitk) seems clever
>> enough to only use the useful part:
>
> The v4.2.0 tag is in origin. I wonder how come you do not have it.
>
>>
>> $ git show randomcrap-ged9e923c3c
Cool, I didn't know this. I usually format it like
ed9e923c3c ("x86: move SMM property to X86MachineState", 2019-12-17)
I can see why most developers don't use "git describe", because at least
those that also are maintainers will often have intermediate tags after
a release.
Anyway I've queued this patch, thanks.
Paolo
prev parent reply other threads:[~2020-01-07 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 8:00 [PATCH] x86: Check for machine state object class before typecasting it Michal Privoznik
2019-12-30 8:06 ` no-reply
2019-12-30 8:41 ` Philippe Mathieu-Daudé
2019-12-30 9:35 ` Michal Prívozník
2019-12-30 9:45 ` Philippe Mathieu-Daudé
2019-12-30 13:17 ` Michal Prívozník
2019-12-30 13:47 ` Philippe Mathieu-Daudé
2020-01-07 10:27 ` Paolo Bonzini [this message]
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=e7b0685b-2444-d7f6-c4ba-2632bd2e4a23@redhat.com \
--to=pbonzini@redhat.com \
--cc=mprivozn@redhat.com \
--cc=mtosatti@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=slp@redhat.com \
/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).