From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] RFC: patch to update git reference policy
Date: Thu, 20 Jan 2011 18:32:56 +0100 [thread overview]
Message-ID: <1295544776.4702.16.camel@tesla.lan> (raw)
In-Reply-To: <4D383627.60804@tresys.com>
Hello Christopher,
thanks for getting back !
On Thu, 20/01/2011 at 08.18 -0500, Christopher J. PeBenito wrote:
> On 01/18/11 19:40, Guido Trentalancia wrote:
> > Hello,
> >
> > I have created a set of two patches to update the git reference policy
> > to run on a generic modern Linux system.
>
> There are too many changes in this patch and the other. Can you
> resubmit, breaking each logically separate change into a different patch?
Yes, I think that can be done, although it might take some time. But
what do you mean exactly for "logically separate" ?
In truth both patches are not logically separated, because of their
common aim to update refpolicy to work on a modern installation more or
less by adding some missing permissions.
I could create a separate patch for each module x (x.fc, x.if, x.te)...
I am not sure this is what you meant. For example, I have (almost) never
created a bidirectional dbus:send_msg permission in a module, but rather
split them in two unidirectional dbus:send_msg permissions in the two
modules that are relevant in that case. So, in this example, splitting
the patch according to modules would break that logic because each
module just implements a unidirectional dbus:send_msg (relative to its
own context only) and the single patch won't completely solve the issue.
Please let me know.
Regards,
Guido
next prev parent reply other threads:[~2011-01-20 17:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 0:40 [refpolicy] RFC: patch to update git reference policy Guido Trentalancia
2011-01-20 13:18 ` Christopher J. PeBenito
2011-01-20 17:32 ` Guido Trentalancia [this message]
2011-01-21 12:37 ` Christopher J. PeBenito
2011-01-24 0:43 ` [refpolicy] [PATCH/RFC 0/19]: patch set to update the " Guido Trentalancia
2011-01-24 15:01 ` Dominick Grift
2011-01-24 15:56 ` Guido Trentalancia
2011-01-24 15:59 ` Dominick Grift
2011-01-24 21:01 ` Guido Trentalancia
2011-01-24 21:22 ` Dominick Grift
[not found] ` <4D471319.2000907@tresys.com>
2011-01-31 21:18 ` Guido Trentalancia
2011-02-02 23:52 ` Martin Orr
2011-02-03 0:04 ` 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=1295544776.4702.16.camel@tesla.lan \
--to=guido@trentalancia.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.