From: Daniel Mierswa <impulze@impulze.org>
To: linux-media@vger.kernel.org
Subject: Re: [RFC PATCH] prevent building/installation of various utilities
Date: Sun, 06 Feb 2011 16:02:52 +0100 [thread overview]
Message-ID: <4D4EB81C.5060706@impulze.org> (raw)
In-Reply-To: <4D47A209.4060805@impulze.org>
On 01.02.2011 07:02, Daniel Mierswa wrote:
> Heya, I wanted to provide a patch to have the ability to _not_ build
> and install various tools even if the requirements are met.
any comments on this? seems rather trivial to decide if it's good to go
or not :D
wrong mailinglist or recipient perhaps?
--
Mierswa, Daniel
If you still don't like it, that's ok: that's why I'm boss. I simply
know better than you do.
--- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22
prev parent reply other threads:[~2011-02-06 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 6:02 [RFC PATCH] prevent building/installation of various utilities Daniel Mierswa
2011-02-06 15:02 ` Daniel Mierswa [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=4D4EB81C.5060706@impulze.org \
--to=impulze@impulze.org \
--cc=linux-media@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