From: Ariel D'Alessandro <ariel@vanguardiasur.com.ar>
To: Hans Verkuil <hverkuil@xs4all.nl>, Sean Young <sean@mess.org>,
Gregor Jasny <gjasny@googlemail.com>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Rosen Penev <rosenp@gmail.com>
Subject: Re: How about a v4l-utils-1.20 release?
Date: Mon, 20 Apr 2020 12:21:52 -0300 [thread overview]
Message-ID: <e71187f6-0796-624b-2c76-010de551a942@vanguardiasur.com.ar> (raw)
In-Reply-To: <f37d4c89-73cb-6efb-ce6b-21a6ae89c559@xs4all.nl>
Hi there,
On 4/20/20 9:35 AM, Hans Verkuil wrote:
> On 20/04/2020 14:19, Sean Young wrote:
>> Hi Gregor,
>>
>> On Mon, Apr 20, 2020 at 02:05:07PM +0200, Gregor Jasny wrote:
>>> Hello,
>>>
>>> It's been a while since we released v4l-utils 1.18. How about a 1.20
>>> release?
>>>
>>> Do you have anything that should go in before?
>>
>> There is nothing from me. There are few patches on the list from Rosen Penev,
>> cleaning up various stuff found with clang.
>
> Ah yes, let me look at those first. I'll do that today.
>
>>
>> Otherwise I guess there is the meson build system, but I don't know how far
>> out that is.
>
> That needs more work.
Agreed with Hans, the meson build system support in not complete yet and
needs to be properly tested.
Regards,
--
Ariel D'Alessandro, VanguardiaSur
www.vanguardiasur.com.ar
next prev parent reply other threads:[~2020-04-20 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 12:05 How about a v4l-utils-1.20 release? Gregor Jasny
2020-04-20 12:07 ` Hans Verkuil
2020-04-20 12:19 ` Sean Young
2020-04-20 12:35 ` Hans Verkuil
2020-04-20 15:21 ` Ariel D'Alessandro [this message]
2020-04-20 12:44 ` Hans Verkuil
2020-04-20 20:03 ` Rosen Penev
2020-05-21 12:05 ` Gregor Jasny
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=e71187f6-0796-624b-2c76-010de551a942@vanguardiasur.com.ar \
--to=ariel@vanguardiasur.com.ar \
--cc=gjasny@googlemail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=rosenp@gmail.com \
--cc=sean@mess.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).