From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Alex Williamson <alex.williamson@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, "Cédric Le Goater" <clg@redhat.com>
Subject: Re: [PATCH 1/2] hw/vfio/migration: Remove unused 'exec/ram_addr.h' header
Date: Wed, 1 Mar 2023 20:32:12 +0100 [thread overview]
Message-ID: <2ede6aca-dce8-d507-5352-d03d5de2dcd4@redhat.com> (raw)
In-Reply-To: <CAFEAcA-Fp8nSZ6iimZH28DXGVWkFbcYv25RvVDdc8WZkBXgfrg@mail.gmail.com>
On 27/02/2023 17.04, Peter Maydell wrote:
> On Mon, 27 Feb 2023 at 15:46, Alex Williamson
> <alex.williamson@redhat.com> wrote:
>>
>> On Mon, 27 Feb 2023 11:32:57 +0100
>> Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
>>
>>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>>
>> Empty commit logs are a pet peeve of mine, there must be some sort of
>> motivation for the change, something that changed to make this
>> possible, or perhaps why this was never necessary. Thanks,
>
> I generally agree, but "this file doesn't actually need to
> include this header" seems straightforward enough that the commit
> subject says everything you'd want to say about it.
But not giving any description at all is really just bad style, we should
avoid it. And in this case, there is even a good reason that should be
mentioned here (e.g. "This header was the only reason this file needed to be
built per target"). So I think it's fair to ask for a proper commit log
message here.
Thomas
next prev parent reply other threads:[~2023-03-01 19:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 10:32 [PATCH 0/2] hw/vfio: Build various target-independent objects once Philippe Mathieu-Daudé
2023-02-27 10:32 ` [PATCH 1/2] hw/vfio/migration: Remove unused 'exec/ram_addr.h' header Philippe Mathieu-Daudé
2023-02-27 13:40 ` Cédric Le Goater
2023-02-27 15:46 ` Alex Williamson
2023-02-27 16:04 ` Peter Maydell
2023-02-27 16:34 ` Alex Williamson
2023-02-27 21:58 ` Philippe Mathieu-Daudé
2023-03-01 19:32 ` Thomas Huth [this message]
2023-02-27 16:24 ` Alex Bennée
2023-02-27 17:13 ` Alex Williamson
2023-03-01 7:47 ` Markus Armbruster
2023-02-27 10:32 ` [PATCH 2/2] hw/vfio: Build various target-independent objects once Philippe Mathieu-Daudé
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=2ede6aca-dce8-d507-5352-d03d5de2dcd4@redhat.com \
--to=thuth@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.