linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	"Serge E. Hallyn" <serue@us.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: capabilities-introduce-per-process-capability-bounding-set.patch breaks FC6 Avahi
Date: Fri, 30 Nov 2007 19:21:03 -0500	[thread overview]
Message-ID: <20071201002103.GA9906@c2.user-mode-linux.org> (raw)
In-Reply-To: <47508EDB.7080205@gmail.com>

On Fri, Nov 30, 2007 at 11:29:47PM +0100, Jiri Slaby wrote:
> Nope, try this :):
> http://lkml.org/lkml/2007/11/28/390

Excellent, thanks.

I just wanted to make sure that someone knew about this.

			Jeff

-- 
Work email - jdike at linux dot intel dot com

      reply	other threads:[~2007-12-01  0:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 19:41 capabilities-introduce-per-process-capability-bounding-set.patch breaks FC6 Avahi Jeff Dike
2007-11-30 22:29 ` Jiri Slaby
2007-12-01  0:21   ` Jeff Dike [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=20071201002103.GA9906@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=akpm@osdl.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).