From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Gregor Jasny <gjasny@googlemail.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, kieran.bingham@ideasonboard.com,
mchehab@kernel.org, nicolas@ndufresne.ca, p.zabel@pengutronix.de,
rosenp@gmail.com, sakari.ailus@iki.fi, sean@mess.org,
user.vdr@gmail.com, xavier.claessens@collabora.com,
deborah.brouwer@collabora.com, ariel@vanguardiasur.com.ar,
ezequiel@vanguardiasur.com.ar, tomi.valkeinen@ideasonboard.com
Subject: Re: [v4l-utils] [PATCH v9 3/7] Add support for meson building
Date: Wed, 22 Feb 2023 13:12:18 +0200 [thread overview]
Message-ID: <Y/X4ktSRZKbHbB1B@pendragon.ideasonboard.com> (raw)
In-Reply-To: <e890fca0-a706-a43d-83ed-80c1f59b1182@googlemail.com>
On Wed, Feb 22, 2023 at 11:41:29AM +0100, Gregor Jasny wrote:
> On 21.02.23 15:51, Laurent Pinchart wrote:
> >> I wonder if we shouldn't make a 1.24 stable release first without this patch
> >> series, then introduce meson with version 1.25. Besides, the last stable release
> >> was 16 months ago, so I think it is high time for a new stable anyway.
> >
> > Works for me.
> >
> >> Gregor, any opinion?
>
> Sure, I can create a new release tonight. Would anyone want to merge
> something prior to the release?
Nothing on my side, I've pushed the meson preparation patches, all I
have remaining is about meson support itself.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-02-22 11:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 14:31 [v4l-utils] [PATCH v9 0/7] Switch build system to meson Laurent Pinchart
2023-02-21 14:31 ` [v4l-utils] [PATCH v9 1/7] utils: Allow choosing v4l2-tracer-gen.pl output Laurent Pinchart
2023-02-21 15:00 ` Hans Verkuil
2023-02-21 15:04 ` Sakari Ailus
2023-02-21 14:31 ` [v4l-utils] [PATCH v9 2/7] Move README to markdown syntax Laurent Pinchart
2023-02-21 14:32 ` [v4l-utils] [PATCH v9 3/7] Add support for meson building Laurent Pinchart
2023-02-21 14:43 ` Hans Verkuil
2023-02-21 14:51 ` Laurent Pinchart
2023-02-22 10:41 ` Gregor Jasny
2023-02-22 11:12 ` Laurent Pinchart [this message]
2023-02-22 17:50 ` Deborah Brouwer
2023-02-22 19:46 ` Hans Verkuil
2023-02-22 19:50 ` Hans Verkuil
2023-02-22 21:12 ` Gregor Jasny
2023-02-22 22:03 ` Hans Verkuil
2023-02-21 14:32 ` [v4l-utils] [PATCH v9 4/7] Copy Doxygen configuration file to doc/ Laurent Pinchart
2023-02-21 14:32 ` [v4l-utils] [PATCH v9 5/7] meson: Add support for doxygen documentation Laurent Pinchart
2023-02-21 14:32 ` [v4l-utils] [PATCH v9 6/7] Drop autoconf/automake support Laurent Pinchart
2023-02-21 14:32 ` [v4l-utils] [PATCH v9 7/7] meson: Use -include to include config.h instead of -I Laurent Pinchart
2023-02-21 14:36 ` [v4l-utils] [PATCH v9 0/7] Switch build system to meson Sakari Ailus
2023-02-21 16:06 ` Sean Young
2023-02-21 16:08 ` [PATCH 1/1] utils: Add help text for v4l2-tracer-gen.pl Sakari Ailus
2023-02-21 16:17 ` Laurent Pinchart
2023-02-21 16:18 ` Hans Verkuil
2023-02-21 18:45 ` Deborah Brouwer
2023-02-22 7:11 ` Sakari Ailus
2023-02-22 8:42 ` Laurent Pinchart
2023-02-23 7:57 ` [v4l-utils] [PATCH v9 0/7] Switch build system to meson Tomi Valkeinen
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=Y/X4ktSRZKbHbB1B@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=ariel@vanguardiasur.com.ar \
--cc=deborah.brouwer@collabora.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=gjasny@googlemail.com \
--cc=hverkuil@xs4all.nl \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
--cc=rosenp@gmail.com \
--cc=sakari.ailus@iki.fi \
--cc=sean@mess.org \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=user.vdr@gmail.com \
--cc=xavier.claessens@collabora.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