All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: Patch series for Kodi 16-Jarvis
Date: Sun, 20 Dec 2015 14:16:13 +0100	[thread overview]
Message-ID: <20151220141613.22b22bdc@free-electrons.com> (raw)
In-Reply-To: <20151220130054.GC3677@free.fr>

Hello,

On Sun, 20 Dec 2015 14:00:54 +0100, Yann E. MORIN wrote:

> Well, I'm not too fond of that. But indeed, it's a pain to review either
> way.
> 
> Maybe a middle-ground solution would be to bump all the screensavers in
> one patch, all the audiocoders in a second one and so on?

I'm fine with this, but I'd like to keep my request to have the "simple
bumps" grouped together in certain commits, but as soon as the bump is
not just a mechanical one, it should be a separate patch. I.e for
example:

	kodi-screensaver-*: mechanical bumps
	kodi-screensaver-baz: bump version

> Also, I'm not too fond of doing reviews on a github repository. I'd
> largely prefer we have a complete RFC series on the list, otherwise the
> reviews are lost. For example, I now can't see what Thomas as said,
> since the branch has been rebased and previous comments are lost.

I think Bernd's intention was just to announce that he was going to
post all the patches as soon as Kodi 16 was out, but he wants to wait
for that release to happen before posting 100 patches on the list.

But by grouping package bumps a little bit, the size of the series
would be a lot shorter, and it would therefore be a bit more acceptable
to post such an RFC series on the list.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-12-20 13:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19 18:05 [Buildroot] RFC: Patch series for Kodi 16-Jarvis Bernd Kuhls
2015-12-20 12:13 ` Bernd Kuhls
2015-12-20 12:54   ` Thomas Petazzoni
2015-12-20 13:00     ` Yann E. MORIN
2015-12-20 13:16       ` Thomas Petazzoni [this message]
2015-12-20 13:48         ` Bernd Kuhls
2015-12-20 14:51           ` Yann E. MORIN
2015-12-20 20:37             ` Bernd Kuhls
2016-01-24 13:44               ` Bernd Kuhls
2016-01-24 14:56                 ` Thomas Petazzoni
2016-01-24 15:18                   ` Bernd Kuhls
2016-01-31 16:38                 ` Bernd Kuhls
2016-02-04 20:39                   ` Bernd Kuhls
2016-02-07 13:41                     ` Bernd Kuhls
2016-02-07 13:58                       ` Thomas Petazzoni
2016-02-13 15:41                         ` Bernd Kuhls
2015-12-20 20:41             ` Bernd Kuhls
2015-12-20 14:47         ` Yann E. MORIN

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=20151220141613.22b22bdc@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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 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.