public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Sami Kerola <kerolasa@iki.fi>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 0/4] pull: allow disabling command builds
Date: Fri, 7 Mar 2014 11:44:29 +0100	[thread overview]
Message-ID: <20140307104429.GC9303@x2.net.home> (raw)
In-Reply-To: <1392564176-11596-1-git-send-email-kerolasa@iki.fi>

On Sun, Feb 16, 2014 at 03:22:52PM +0000, Sami Kerola wrote:
> This pull request has four patches that will allow a builder to disable
> all commands. 

Note that I don't silently ignore these patches, but I'd like to play
with it later and try to provide better granularity, maybe something
like

  --enable-util=<list>
  --disable-util=<list>
  --enable-all
  --disable-all

where <list> is comma separated list of the utils names (we already
use thing like this for static programs), then we can avoid huge
number of --enable-* options.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  parent reply	other threads:[~2014-03-07 10:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-16 15:22 [PATCH 0/4] pull: allow disabling command builds Sami Kerola
2014-02-16 15:22 ` [PATCH 1/4] build-sys: allow per directory build targets Sami Kerola
2014-02-16 15:22 ` [PATCH 2/4] build-sys: add libs-only to config-gen.d Sami Kerola
2014-02-16 15:22 ` [PATCH 3/4] tools: make config-gen to require build target argument Sami Kerola
2014-03-07 10:54   ` Karel Zak
2014-02-16 15:22 ` [PATCH 4/4] tests: check commands needed for running a test exist Sami Kerola
2014-03-07 10:55   ` Karel Zak
2014-03-07 10:44 ` Karel Zak [this message]
2014-03-07 14:52   ` [PATCH 0/4] pull: allow disabling command builds Sami Kerola

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=20140307104429.GC9303@x2.net.home \
    --to=kzak@redhat.com \
    --cc=kerolasa@iki.fi \
    --cc=util-linux@vger.kernel.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