All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	Joshua Brindle <jbrindle@tresys.com>,
	SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Latest policycoreutils patch
Date: Thu, 19 Jan 2006 09:27:01 -0500	[thread overview]
Message-ID: <43CFA1B5.20601@redhat.com> (raw)
In-Reply-To: <43CE9E81.3000706@cornell.edu>

Ivan Gyurdiev wrote:
>
>> Not sure I follow; the patch changes some occurrences of "Failed to add
>> port" to "Failed to modify port" in the add() method.
>>   
> ...which is wrong, imho, it should still say "Failed to add port".
> The second part of it is right, I think (I assume it's changing 
> modify(), hard to tell without the -p flag).
> There's a bug in modify that says "failed to add" currently.
>
> I agree with what Dan is saying, I just think the first place he's 
> changing is wrong.
>
Yes the first part of the patch is wrong.  The messsage under the add 
section should stay add.  I was changing the "add" to "modify" under the 
modify section and got carried away...
> There's another wrong message btw, see interfaces.modify().
>


--
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.

  reply	other threads:[~2006-01-19 14:27 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 20:34 Latest policycoreutils patch Daniel J Walsh
2006-01-18  1:36 ` Joshua Brindle
2006-01-18  1:37 ` Joshua Brindle
2006-01-18  3:40   ` Daniel J Walsh
2006-01-18  3:41     ` Joshua Brindle
2006-01-18  3:48       ` Daniel J Walsh
2006-01-18  3:51         ` Joshua Brindle
2006-01-18  7:02           ` Ivan Gyurdiev
2006-01-18 15:44             ` Daniel J Walsh
2006-01-18 18:00               ` Ivan Gyurdiev
2006-01-18 18:12                 ` Ivan Gyurdiev
2006-01-18 18:30                   ` Stephen Smalley
2006-01-18 18:36                     ` Ivan Gyurdiev
2006-01-18 18:52                       ` Stephen Smalley
2006-01-18 19:04                         ` Ivan Gyurdiev
2006-01-18 19:32                           ` Stephen Smalley
2006-01-18 19:07                         ` Daniel J Walsh
2006-01-18 19:15                           ` Ivan Gyurdiev
2006-01-18 19:19                             ` Daniel J Walsh
2006-01-18 19:59                               ` Stephen Smalley
2006-01-18 20:01                                 ` Ivan Gyurdiev
2006-01-19 14:27                                   ` Daniel J Walsh [this message]
2006-01-18 16:13 ` Stephen Smalley
  -- strict thread matches above, loose matches on Subject: below --
2006-09-07 13:31 Daniel J Walsh
2006-09-08 14:00 ` Karl MacMillan
2006-09-08 14:33 ` Joshua Brindle
2006-09-08 14:55   ` Karl MacMillan
2006-09-08 14:35 ` Stephen Smalley
2006-09-08 16:37   ` Daniel J Walsh
2006-09-08 20:25     ` Stephen Smalley
2006-09-11 12:25       ` Joshua Brindle
2006-09-12 12:45         ` Karl MacMillan
2006-09-13 15:14       ` Joshua Brindle
2006-11-06 15:25 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=43CFA1B5.20601@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=ivg2@cornell.edu \
    --cc=jbrindle@tresys.com \
    --cc=sds@tycho.nsa.gov \
    --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.