qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: "Peter Krempa" <pkrempa@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-block@nongnu.org, libvir-list@redhat.com,
	qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH v2 1/1] IDE: deprecate ide-drive
Date: Thu, 10 Oct 2019 14:08:12 -0400	[thread overview]
Message-ID: <1a35d92f-ccb1-9e54-193b-a1b193c3e696@redhat.com> (raw)
In-Reply-To: <20191010115436.GS6129@angien.pipo.sk>



On 10/10/19 7:54 AM, Peter Krempa wrote:
> On Thu, Oct 10, 2019 at 13:42:26 +0200, Philippe Mathieu-Daudé wrote:
>> On 10/10/19 1:26 PM, Peter Krempa wrote:
>>> On Thu, Oct 10, 2019 at 13:22:37 +0200, Philippe Mathieu-Daudé wrote:
>>>> On 10/10/19 12:43 AM, John Snow wrote:
>>>>> It's an old compatibility shim that just delegates to ide-cd or ide-hd.
>>>>> I'd like to refactor these some day, and getting rid of the super-object
>>>>> will make that easier.
>>>>>
>>>>> Either way, we don't need this.
>>>>>
>>>>> Libvirt-checked-by: Peter Krempa <pkrempa@redhat.com>
>>>>
>>>> Peter made a comment regarding Laszlo's Regression-tested-by tag:
>>>>
>>>>    [...] nobody else is using
>>>>    this convention (there are exactly 0 instances of
>>>>    "Regression-tested-by" in the project git log as far as
>>>>    I can see), and so in practice people reading the commits
>>>>    won't really know what you meant by it. Everybody else
>>>>    on the project uses "Tested-by" to mean either of the
>>>>    two cases you describe above, without distinction...
>>>>
>>>> It probably applies to 'Libvirt-checked-by' too.
>>>
>>> I certainly didn't test it. So feel free to drop that line altogether.
>>
>> But you reviewed it, can we use your 'Reviewed-by' instead?
> 
> To be honest, I didn't really review the code nor the documentation.
> I actually reviewed only the idea itself in the context of integration
> with libvirt and that's why I didn't go for 'Reviewed-by:'.
> 
> The gist of the citation above is that we should stick to well known
> tags with their well known meanings and I think that considering this a
> 'review' would be a stretch of the definiton.
> 

I wasn't aware that PMM wanted to avoid non-standard tags; I consider
them to be for human use, but I can change that behavior.

Peter, I'll change it to an ACK (as suggested by Kevin) is that's OK by you.

--js


  parent reply	other threads:[~2019-10-10 18:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 22:43 [PATCH v2 0/1] IDE: Deprecate ide-drive John Snow
2019-10-09 22:43 ` [PATCH v2 1/1] IDE: deprecate ide-drive John Snow
2019-10-10  7:44   ` Thomas Huth
2019-10-10  8:49   ` Markus Armbruster
2019-10-10 11:22   ` Philippe Mathieu-Daudé
2019-10-10 11:26     ` Peter Krempa
2019-10-10 11:42       ` Philippe Mathieu-Daudé
2019-10-10 11:54         ` Peter Krempa
2019-10-10 12:40           ` Kevin Wolf
2019-10-10 18:08           ` John Snow [this message]
2019-10-11  9:12             ` Peter Krempa
2019-10-11 20:44               ` John Snow

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=1a35d92f-ccb1-9e54-193b-a1b193c3e696@redhat.com \
    --to=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=pkrempa@redhat.com \
    --cc=qemu-block@nongnu.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 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).