All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ariel D'Alessandro <ariel@vanguardiasur.com.ar>
To: Gregor Jasny <gjasny@googlemail.com>,
	Xavier Claessens <xavier.claessens@collabora.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Ezequiel Garcia <ezequiel@collabora.com>
Cc: kieran.bingham@ideasonboard.com, linux-media@vger.kernel.org,
	hverkuil@xs4all.nl, sean@mess.org, p.zabel@pengutronix.de,
	nicolas@ndufresne.ca,
	nicolas Dufresne <nicolas.dufresne@collabora.com>
Subject: Re: [PATCH v1 1/1] Add support for meson building
Date: Thu, 2 Jul 2020 23:15:07 -0300	[thread overview]
Message-ID: <5c81e992-f1a9-f70b-f43b-5c99cca4b8b4@vanguardiasur.com.ar> (raw)
In-Reply-To: <1497236f-6b21-922d-efe1-a0d4a44fc6f5@googlemail.com>



On 6/29/20 3:44 PM, Gregor Jasny wrote:
> 
> 
> On 6/25/20 8:32 PM, Ariel D'Alessandro wrote:
>> Hey Gregor,
>>
>> On 6/24/20 4:46 PM, Gregor Jasny wrote:
>>> Hello,
>>>
>>> thanks for your helpful suggestions. I made a PR from those: Feel free to squash
>>> it into yours:
>>> https://gitlab.com/adalessandro/v4l-utils/-/merge_requests/1
>>>
>>> When looking at your quoted code with the fixes I'm wondering if you forgot to
>>> push your branch?
>>
>> Merged and pushed, thanks.
> 
> From a Debian packager perspective the current branch looks really good. Only
> lintian found a small typo:
> 
> I: qv4l2: image-file-has-conflicting-name
> usr/share/icons/hicolor/scalable/apps/qv4l2.svg (is PNG)
> 
> 
> I guess it's due to that:
> 
> qv4l2_icons_files = [
> ...
>     ['qv4l2.png',       'scalable', 'qv4l2.svg'],
> ]

Great. Fixed both in qvidcap and qv4l2.

Thanks,
Ariel

  reply	other threads:[~2020-07-03  2:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 13:33 [PATCH v1 0/1] Add support for meson building Ariel D'Alessandro
2020-06-18 13:33 ` [PATCH v1 1/1] " Ariel D'Alessandro
2020-06-18 13:57   ` Kieran Bingham
2020-06-18 14:06     ` Laurent Pinchart
2020-06-18 14:11       ` Kieran Bingham
2020-06-19 14:12     ` Ezequiel Garcia
2020-06-19 14:42       ` Laurent Pinchart
2020-06-19 18:40         ` Xavier Claessens
2020-06-20  4:45           ` VDRU VDRU
2020-06-22 18:07           ` Gregor Jasny
2020-06-22 19:09             ` Gregor Jasny
2020-06-23 17:26               ` Ariel D'Alessandro
2020-06-24 19:46                 ` Gregor Jasny
2020-06-25 18:32                   ` Ariel D'Alessandro
2020-06-29 18:44                     ` Gregor Jasny
2020-07-03  2:15                       ` Ariel D'Alessandro [this message]
2020-06-25 18:52                 ` Ariel D'Alessandro
2020-06-29 18:56                   ` Gregor Jasny
2020-07-08  5:48                     ` Ariel D'Alessandro
2020-07-16 19:48                       ` Gregor Jasny
2020-06-19 19:04       ` Xavier Claessens
2020-06-22 19:19     ` Ariel D'Alessandro
2020-06-19 12:10 ` [PATCH v1 0/1] " Sean Young
2020-06-19 14:09   ` Ezequiel Garcia

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=5c81e992-f1a9-f70b-f43b-5c99cca4b8b4@vanguardiasur.com.ar \
    --to=ariel@vanguardiasur.com.ar \
    --cc=ezequiel@collabora.com \
    --cc=gjasny@googlemail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=nicolas.dufresne@collabora.com \
    --cc=nicolas@ndufresne.ca \
    --cc=p.zabel@pengutronix.de \
    --cc=sean@mess.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.