From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: "Václav Ovsík" <vaclav.ovsik@i.cz>
Cc: <selinux@tycho.nsa.gov>, <selinux-devel@lists.alioth.debian.org>
Subject: Re: refpolicy: patch for ldconfig from glibc 2.7
Date: Mon, 25 Feb 2008 08:40:19 -0500 [thread overview]
Message-ID: <1203946819.32061.34.camel@gorn> (raw)
In-Reply-To: <20080225124131.GB31035@bobek.pm.i.cz>
On Mon, 2008-02-25 at 13:41 +0100, Václav Ovsík wrote:
> On Fri, Feb 22, 2008 at 01:05:39PM -0500, Christopher J. PeBenito wrote:
> > This is the right fix, and basically the same fix is queued up for
> > merging as part of Dan's patch set.
>
> Ok. Should I stop to send patches based on the Dan's Fedora policy?
No.
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2008-02-25 13:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 15:27 refpolicy: patch for ldconfig from glibc 2.7 Václav Ovsík
2008-02-22 18:05 ` Christopher J. PeBenito
2008-02-25 12:41 ` Václav Ovsík
2008-02-25 13:40 ` Christopher J. PeBenito [this message]
2008-02-25 14:38 ` Daniel J Walsh
2008-02-29 7:21 ` refpolicy: patch for ldconfig from glibc 2.7, new patch Václav Ovsík
2008-02-29 13:46 ` Christopher J. PeBenito
2008-02-29 15:29 ` [DSE-Dev] " Martin Orr
2008-02-29 16:32 ` Christopher J. PeBenito
2008-03-01 14:54 ` Martin Orr
2008-03-04 19:39 ` [DSE-Dev] refpolicy: patch for ldconfig from glibc2.7, " Christopher J. PeBenito
2008-03-04 15:19 ` refpolicy: patch for ldconfig from glibc 2.7, " Václav Ovsík
2008-03-04 15:37 ` [DSE-Dev] " Václav Ovsík
2008-08-12 15:30 ` refpolicy: patch for ldconfig from glibc 2.7 Václav Ovsík
2008-08-12 19:38 ` Christopher J. PeBenito
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=1203946819.32061.34.camel@gorn \
--to=cpebenito@tresys.com \
--cc=selinux-devel@lists.alioth.debian.org \
--cc=selinux@tycho.nsa.gov \
--cc=vaclav.ovsik@i.cz \
/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.