From: Ivan Gyurdiev <ivg2@cornell.edu>
To: selinux@tycho.nsa.gov
Cc: Joshua Brindle <jbrindle@tresys.com>
Subject: Re: Record keys
Date: Sat, 15 Oct 2005 05:33:48 -0400 [thread overview]
Message-ID: <4350CCFC.80900@cornell.edu> (raw)
In-Reply-To: <434F5E8C.1050708@cornell.edu>
>
>> Please help me decide what to do with the record key for the record
>> structures which I've added into libsepol and libsemanage. Stephen
>> has now exported those functions into the shared library, so after an
>> official release, it would be good not to be changing those APIs.
Joshua? No comments?
(see original message for details)
If nobody suggests anything, I am likely to leave the key in, and add a
key_unpack function, and pass the key down to the sepol level....
--
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:[~2005-10-15 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <434F5E3A.5030003@cornell.edu>
2005-10-14 7:30 ` Record keys Ivan Gyurdiev
2005-10-15 9:33 ` Ivan Gyurdiev [this message]
2005-10-19 14:02 ` Joshua Brindle
2005-10-19 16:50 ` Ivan Gyurdiev
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=4350CCFC.80900@cornell.edu \
--to=ivg2@cornell.edu \
--cc=jbrindle@tresys.com \
--cc=selinux@tycho.nsa.gov \
/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.