From: paul.moore@hp.com (Paul Moore)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] filesystem: btrfs enablement
Date: Fri, 16 Jan 2009 17:08:26 -0500 [thread overview]
Message-ID: <20090116220832.907766616@hp.com> (raw)
An embedded and charset-unspecified text was scrubbed...
Name: btrfs-enable
Url: http://oss.tresys.com/pipermail/refpolicy/attachments/20090116/639f9892/attachment.pl
next reply other threads:[~2009-01-16 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 22:08 Paul Moore [this message]
2009-01-21 20:24 ` [refpolicy] filesystem: btrfs enablement Daniel J Walsh
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=20090116220832.907766616@hp.com \
--to=paul.moore@hp.com \
--cc=refpolicy@oss.tresys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.