From: Hans de Goede <hdegoede@redhat.com>
To: Gregor Jasny <gjasny@googlemail.com>,
linux-media@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Subject: Re: v4l-utils stable release 1.6.1
Date: Thu, 20 Nov 2014 21:22:03 +0100 [thread overview]
Message-ID: <546E4D6B.30100@redhat.com> (raw)
In-Reply-To: <546E093D.4030203@googlemail.com>
Hi,
On 11/20/2014 04:31 PM, Gregor Jasny wrote:
> Hello,
>
> do you consider something from these commits as important enough for a bugfix release?
>
<snip>
>> Hans de Goede (2):
>> rc_keymaps: allwinner: S/KEY_HOME/KEY_HOMEPAGE/
>> v4lconvert: Fix decoding of jpeg data with no vertical sub-sampling
Yes both of them (first one is not that important, but if you're doing
a 1.6.1 anyways it is good to include it).
Regards,
Hans
next prev parent reply other threads:[~2014-11-20 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 15:31 v4l-utils stable release 1.6.1 Gregor Jasny
2014-11-20 16:15 ` Mauro Carvalho Chehab
2014-11-20 20:22 ` Hans de Goede [this message]
2014-11-21 19:37 ` Hans Verkuil
2014-11-21 20:03 ` v4l-utils stable release 1.6.2 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=546E4D6B.30100@redhat.com \
--to=hdegoede@redhat.com \
--cc=gjasny@googlemail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.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;
as well as URLs for NNTP newsgroup(s).