From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/pkg-kconfig: define KCONFIG_EDITORS_MAKE_ENV
Date: Thu, 2 Jul 2015 09:52:17 +0200 [thread overview]
Message-ID: <20150702095217.6813b8c5@free-electrons.com> (raw)
In-Reply-To: <1435823045.2966.23.camel@synopsys.com>
Dear Alexey Brodkin,
On Thu, 2 Jul 2015 07:44:05 +0000, Alexey Brodkin wrote:
> I'm wondering why did you put 2 patches in one series?
> [1] https://patchwork.ozlabs.org/patch/489307/
> [2] https://patchwork.ozlabs.org/patch/489306/
>
> I'd say these 2 patches solve completely different problems and so
> should be posted as 2 separate patches compared to your [PATCH 1/2],
> [PATCH 2/2].
I agree they are not related.
> The problem with series patches within series could not be applied
> separately, that means chances are you may not get either applied
> because:
That's not really true. I tend to try to apply all patches I can from a
series, even if certain other patches of the series cannot be applied.
Look at the SELinux series for example. I have not applied some of the
first patches of the series, but already applied some patches later in
the series.
So while I agree it's a bit weird to mix completely independent stuff in
one single patch series, it's not actually that problematic.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-02 7:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 12:50 [Buildroot] [PATCH 1/2] package/gcc: fix ARC failure to build in 2 phases Tal Zilcer
2015-06-29 12:50 ` [Buildroot] [PATCH 2/2] package/pkg-kconfig: define KCONFIG_EDITORS_MAKE_ENV Tal Zilcer
2015-07-02 7:44 ` Alexey Brodkin
2015-07-02 7:52 ` Thomas Petazzoni [this message]
2015-07-02 7:56 ` Alexey Brodkin
2015-06-29 14:29 ` [Buildroot] [PATCH 1/2] package/gcc: fix ARC failure to build in 2 phases Thomas Petazzoni
2015-06-29 15:39 ` Tal Zilcer
2015-06-29 15:49 ` Thomas Petazzoni
2015-07-02 7:46 ` Alexey Brodkin
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=20150702095217.6813b8c5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox