qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Brad Smith <brad@comstyle.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] tap-bsd: Remove special casing for older OpenBSD releases
Date: Thu, 6 May 2021 10:19:31 +0800	[thread overview]
Message-ID: <e5df409d-2560-131d-420f-db38b148cbd7@redhat.com> (raw)
In-Reply-To: <78602d9d-e111-05f0-c91d-debb6e78009f@comstyle.com>


在 2021/5/2 下午12:10, Brad Smith 写道:
> On 4/1/2021 3:24 AM, Jason Wang wrote:
>>
>> 在 2021/3/30 上午4:38, Brad Smith 写道:
>>> On 3/28/2021 11:58 PM, Jason Wang wrote:
>>>
>>>>
>>>> 在 2021/3/29 上午11:03, Brad Smith 写道:
>>>>> It very much is correct. We don't care about such releases anymore.
>>>>
>>>>
>>>> So is there a doc/wiki to say Qemu doesn't support those OpenBSD 
>>>> release?
>>>
>>> The (OpenBSD itself and QEMU) project only makes a concerted effort 
>>> to support
>>> two previous releases. I can't remember where in the QEMU Wiki it is 
>>> mentioned.
>>>
>>> Just looking at the Meson requirement alone limits us to the 
>>> previous two releases
>>> never mind older. Even if that wasn't a consideration there would be 
>>> issues with
>>> a few other dependencies like Gtk before going back this far to 
>>> support such old
>>> OpenBSD releases.
>>>
>>>
>>
>> Ok. So I've applied this patch.
>>
>> Thanks
>
>
> I do not see where.


I don't queue it for 6.0 so it will be in the next pull request.

Thanks




  reply	other threads:[~2021-05-06  2:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 23:49 [PATCH] tap-bsd: Remove special casing for older OpenBSD releases Brad Smith
2021-03-29  2:22 ` Jason Wang
2021-03-29  3:03   ` Brad Smith
2021-03-29  3:58     ` Jason Wang
2021-03-29 20:38       ` Brad Smith
2021-04-01  7:24         ` Jason Wang
2021-05-02  4:10           ` Brad Smith
2021-05-06  2:19             ` Jason Wang [this message]
2021-05-06  3:16               ` Brad Smith

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=e5df409d-2560-131d-420f-db38b148cbd7@redhat.com \
    --to=jasowang@redhat.com \
    --cc=brad@comstyle.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).