From: Gregor Jasny <gjasny@googlemail.com>
To: Sean Young <sean@mess.org>
Cc: linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@s-opensource.com>
Subject: Re: Time for a v4l-utils 1.12 release
Date: Mon, 16 Jan 2017 21:00:40 +0100 [thread overview]
Message-ID: <2e009306-bb2b-1c43-fa99-dc0974696e19@googlemail.com> (raw)
In-Reply-To: <20170116100656.GA23993@gofer.mess.org>
On 16/01/2017 11:06, Sean Young wrote:
> On Mon, Jan 16, 2017 at 09:10:36AM +0100, Gregor Jasny wrote:
>> Hello,
>>
>> I'd like to do a new v4l-utils release before the Debian freeze. Is master
>> in a releasable state? Or should I wait for some more patches to land?
>
> This pull request is still waiting to be merged.
>
> https://patchwork.linuxtv.org/patch/38830/
As far as I can tell this looks good. Merged.
next prev parent reply other threads:[~2017-01-16 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 8:10 Time for a v4l-utils 1.12 release Gregor Jasny
2017-01-16 10:06 ` Sean Young
[not found] ` <CAN5H-g5GNkkeJ87Gcz1YknGpevk278S=gkLCdYX9RquwqaXQog@mail.gmail.com>
2017-01-16 19:41 ` Gregor Jasny
2017-01-16 20:00 ` Gregor Jasny [this message]
2017-01-19 17:16 ` Sean Young
2017-01-16 11:24 ` Hans Verkuil
2017-01-16 19:42 ` Gregor Jasny
2017-01-17 7:31 ` Hans Verkuil
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=2e009306-bb2b-1c43-fa99-dc0974696e19@googlemail.com \
--to=gjasny@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@s-opensource.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