From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 10/16] libcgroup: new package
Date: Tue, 1 Oct 2013 23:14:01 +0200 [thread overview]
Message-ID: <20131001231401.2856aca6@skate> (raw)
In-Reply-To: <OF65F0E18D.9A0E7DE2-ON86257BF7.006E0B8B-86257BF7.006E4047@rockwellcollins.com>
Clayton,
On Tue, 1 Oct 2013 15:04:47 -0500, clshotwe at rockwellcollins.com wrote:
> > Maybe you want to resend just this patch with those fixes, so we can
> > get it merged quickly, independently of the other SELinux changes.
>
> Should I do that with all of the simple patches?
It's a matter of strategy. When a relatively simple patch is part of a
larger, more complicated patch series, then it is unlikely to get
committed until the entire patch series gets committed. So,
strategically speaking, you might want to progressively reduce the size
of your patch series by merging parts of it that are independent of the
rest of the series, but are needed for it. Your libcgroup package is a
good candidate :)
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-01 21:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 19:32 [Buildroot] [PATCH v3 00/16] SELinux Buildroot Additions Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 01/16] pcre: Add host build support Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 02/16] libselinux: new package Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 03/16] ustr: " Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 04/16] bzip2: Add host build shared library installation Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 05/16] libsemanage: new package Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 06/16] checkpolicy: " Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 07/16] sepolgen: " Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 08/16] sqlite: Add host build support Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 09/16] setools: new package Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 10/16] libcgroup: " Clayton Shotwell
2013-10-01 19:48 ` Thomas Petazzoni
2013-10-01 20:04 ` clshotwe at rockwellcollins.com
2013-10-01 21:14 ` Thomas Petazzoni [this message]
2013-09-25 19:32 ` [Buildroot] [PATCH v3 11/16] python-pyparsing: Add host build option Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 12/16] audit: new package Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 13/16] policycoreutils: " Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 14/16] python-pyxml: " Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 15/16] refpolicy: " Clayton Shotwell
2013-09-25 19:32 ` [Buildroot] [PATCH v3 16/16] shadow: " Clayton Shotwell
2013-10-01 19:51 ` [Buildroot] [PATCH v3 00/16] SELinux Buildroot Additions Thomas Petazzoni
2013-10-01 20:32 ` clshotwe at rockwellcollins.com
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=20131001231401.2856aca6@skate \
--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