Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v1] package/gst1-plugins-bad: add webrtcbin option
Date: Sat, 16 Mar 2019 22:55:31 +0100	[thread overview]
Message-ID: <20190316225531.1eee0726@gmx.net> (raw)
In-Reply-To: <20190314085445.7be54f55@windsurf>

Hello Arnout, Thomas,

On Thu, 14 Mar 2019 08:54:45 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> On Thu, 14 Mar 2019 08:27:56 +0100
> Arnout Vandecappelle <arnout@mind.be> wrote:
> 
> >  The Config.in option was introduced in 2017.02, and renamed for 2017.08.
> > 
> >  However, the rename was also backported to 2017.02.4.
> > 
> >  In other words, the only people who could be hit by this issue are people that
> > used 2017.02 and never upgraded even to 2017.02.4.
> > 
> >  I think it's OK if we risk breaking something for those people. Especially
> > because the problem is very obvious and very easy to fix.  
> 
> Yes, I agree: I believe it's better to have the right name for the
> option moving forward, and the problem with re-using the name of the
> previous option is not too bad.
> 
> So, I'm happy to see that both of us agree on the direction to take
> with this.

To both: thanks for review and advice, updated patch follows...

Regards,
Peter

> 
> Thanks
> 
> Thomas

      reply	other threads:[~2019-03-16 21:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 17:51 [Buildroot] [RFC v1] package/gst1-plugins-bad: add webrtcbin option Peter Seiderer
2019-03-12 21:27 ` Thomas Petazzoni
2019-03-13  9:05   ` Arnout Vandecappelle
2019-03-13 19:17     ` Peter Seiderer
2019-03-14  7:27       ` Arnout Vandecappelle
2019-03-14  7:54         ` Thomas Petazzoni
2019-03-16 21:55           ` Peter Seiderer [this message]

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=20190316225531.1eee0726@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /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