From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/3] fc_sort: fix typos in comments
Date: Fri, 4 Apr 2014 15:51:41 -0400 [thread overview]
Message-ID: <533F0D4D.3080209@tresys.com> (raw)
In-Reply-To: <1395608499-9916-1-git-send-email-nicolas.iooss@m4x.org>
On 03/23/2014 05:01 PM, Nicolas Iooss wrote:
> ---
> support/fc_sort.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/support/fc_sort.c b/support/fc_sort.c
> index e03ef3b..29e2ce9 100644
> --- a/support/fc_sort.c
> +++ b/support/fc_sort.c
> @@ -81,7 +81,7 @@ typedef struct file_context_bucket {
> * -> a is less specific than b.
> * If a's string length is shorter than b's string length,
> * -> a is less specific than b.
> - * If a does not have a specified type and b does not,
> + * If a does not have a specified type and b does,
> * -> a is less specific than b.
> */
> int fc_compare(file_context_node_t *a, file_context_node_t *b)
> @@ -496,7 +496,7 @@ int main(int argc, char *argv[])
> bcurrent->data = current;
> current = current->next;
>
> - /* Detatch the node in the bucket from the old list. */
> + /* Detach the node in the bucket from the old list. */
> bcurrent->data->next = NULL;
>
> /* If there should be another bucket, put one at the end. */
>
This set is merged.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2014-04-04 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 21:01 [refpolicy] [PATCH 1/3] fc_sort: fix typos in comments Nicolas Iooss
2014-03-23 21:01 ` [refpolicy] [PATCH 2/3] fc_sort: initialize allocated memory to fix execution on an empty file Nicolas Iooss
2014-03-23 21:01 ` [refpolicy] [PATCH 3/3] fc_sort: make outfile argument optional Nicolas Iooss
2014-04-04 19:51 ` Christopher J. PeBenito [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=533F0D4D.3080209@tresys.com \
--to=cpebenito@tresys.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.