From: Joshua Brindle <method@manicmethod.com>
To: Guido Trentalancia <guido@trentalancia.com>
Cc: Eamon Walsh <ewalsh@tycho.nsa.gov>, SELinux@tycho.nsa.gov
Subject: Re: [PATCH] Support for long-options in policycoreutils and checkpolicy (Ticket #1 [1672486])
Date: Fri, 27 Nov 2009 13:42:52 -0500 [thread overview]
Message-ID: <4B101DAC.5080801@manicmethod.com> (raw)
In-Reply-To: <1258841039.3002.214.camel@tesla.lan>
Guido Trentalancia wrote:
> Dear Eamon,
>
> here are the two "maintenance" patches that I did post earlier this
> month (along with the new manual pages). They are intended to close
> Ticket #1 [1672486] that I found open on Tresys pages
> (http://userspace.selinuxproject.org/trac/ticket/1).
>
> I do apologize for not putting the keyword "[PATCH]" in the original
> message.
>
> Here is a summary of what has been changed for policycoreutils:
>
> - introduced proper handling of -h, -V options and their respective long
> formats --help and --version to all binaries that are produced from C
> code. The same issue is not tackled for Python-based tools (e.g.
> semanage);
> - relative manual pages have also been updated accordingly.
>
> And here is what has been changed for checkpolicy/checkmodule:
>
> - introduced proper handling of -h, -V and the long formats --help and
> --version to all binaries (checkpolicy/checkmodule);
> - introduced the handling of long options for some of the other
> available options;
> - manual pages have also been updated accordingly (and a few
> undocumented options have been documented).
>
> One of the original two patches (the one against policycoreutils) did
> not compile cleanly anymore against the current HEAD of SELinux, so I
> have created an updated one, which is the one attached here.
>
> It's just a matter of some really minor issues, but I hope it helps, at
> least the ticket can now be closed...
>
> Kind regards,
>
> Guido
>
Thank you for doing this. Unfortunately it looks like your mail client
decided to base64 encode the attachment.
It is always best to use git to generate patch emails, please see:
http://andrewprice.me.uk/weblog/entry/generating-patch-emails-with-git
--
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:[~2009-11-27 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 23:57 Contributed manual pages for libselinux Guido Trentalancia
2009-11-21 2:42 ` Eamon Walsh
2009-11-21 19:51 ` Guido Trentalancia
2009-11-27 19:23 ` Joshua Brindle
2009-11-27 20:03 ` Joshua Brindle
2009-11-21 22:03 ` [PATCH] Support for long-options in policycoreutils and checkpolicy (Ticket #1 [1672486]) Guido Trentalancia
2009-11-27 18:42 ` Joshua Brindle [this message]
2009-11-27 19:07 ` Joshua Brindle
2009-11-28 1:56 ` Guido Trentalancia
2009-11-28 1:58 ` Guido Trentalancia
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=4B101DAC.5080801@manicmethod.com \
--to=method@manicmethod.com \
--cc=SELinux@tycho.nsa.gov \
--cc=ewalsh@tycho.nsa.gov \
--cc=guido@trentalancia.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.