public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sean Young <sean@mess.org>
Cc: Gregor Jasny <gjasny@googlemail.com>,
	linux-media@vger.kernel.org, hverkuil@xs4all.nl,
	mchehab@kernel.org
Subject: Re: [v4l-utils] [PATCH v10 1/5] Add support for meson building
Date: Mon, 13 Mar 2023 12:15:48 +0200	[thread overview]
Message-ID: <20230313101548.GF2545@pendragon.ideasonboard.com> (raw)
In-Reply-To: <ZA7oQMz24B+vDN5V@gofer.mess.org>

On Mon, Mar 13, 2023 at 09:09:20AM +0000, Sean Young wrote:
> On Mon, Mar 13, 2023 at 08:57:21AM +0100, Gregor Jasny wrote:
> > Hello,
> > 
> > On 12.03.23 15:49, Laurent Pinchart wrote:
> > > Will you submit the patch to the linux-media mailing list ?
> > 
> > after fighting more than one hour with git send-email and Google Mail I
> > finally gave up and pushed the patches to the master branch.
> > 
> > /me wishes for:
> > * a low-entry barrier patch submitting mechanism
> > * a nice CI system with configuration-as-code
> > * a bug tracker
> 
> Me too. 
> 
>  - Would save a lot of time, submitting patches is too manual
>  - Make make things much easier to track
>  - CI would undoubtedly improve code quality
>  - Too hard for users to submit bugs
>  - much more..
> 
> gitlab would be great for v4l-utils, I think.

I'm fine with gitlab as a hosting, submission and CI system. Give me a
way to push a branch to gitlab and still have all reviews on the
linux-media mailing list, and I'll be fine :-)

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2023-03-13 10:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 16:44 [v4l-utils] [PATCH v10 0/5] Switch build system to meson Laurent Pinchart
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 1/5] Add support for meson building Laurent Pinchart
2023-03-12 14:31   ` Gregor Jasny
2023-03-12 14:49     ` Laurent Pinchart
2023-03-13  7:57       ` Gregor Jasny
2023-03-13  8:11         ` Laurent Pinchart
2023-03-14  7:03           ` Gregor Jasny
2023-03-18 18:17             ` Mauro Carvalho Chehab
2023-03-18 23:06               ` Laurent Pinchart
2023-03-19  0:20                 ` Mauro Carvalho Chehab
2023-03-13  9:09         ` Sean Young
2023-03-13 10:15           ` Laurent Pinchart [this message]
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 2/5] Copy Doxygen configuration file to doc/ Laurent Pinchart
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 3/5] meson: Add support for doxygen documentation Laurent Pinchart
2023-03-20 11:38   ` Mauro Carvalho Chehab
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 4/5] Drop autoconf/automake support Laurent Pinchart
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 5/5] meson: Use -include to include config.h instead of -I Laurent Pinchart

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=20230313101548.GF2545@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=gjasny@googlemail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --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