From: Nicolas Iooss <nicolas.iooss@m4x.org>
To: Chris PeBenito <pebenito@ieee.org>
Cc: Dominick Grift <dac.override@gmail.com>,
selinux-refpolicy@vger.kernel.org,
Russell Coker <russell@coker.com.au>
Subject: Re: [PATCH] systemd related interfaces
Date: Fri, 11 Jan 2019 00:10:36 +0100 [thread overview]
Message-ID: <CAJfZ7=nDEFBe+amDqAhnrOoaWcK=82kLz=BQeBuoMZqPpfxnvw@mail.gmail.com> (raw)
In-Reply-To: <7c7cec36-0636-6356-da44-d505951397e0@ieee.org>
On Tue, Jan 8, 2019 at 12:37 AM Chris PeBenito <pebenito@ieee.org> wrote:
>
> On 1/6/19 5:10 PM, Nicolas Iooss wrote:
> > By the way, I do pull requests because I find them simpler to handle
> > from my side (because I have too many emails in my inbox), but if you
> > prefer that I post the patches on the list, I can do that instead. It
> > would be useful for the project to have a CONTRIBUTING file describing
> > the preferred way of sending patches or reporting issues, or to have
> > such information in the README file.
>
> It is described here:
>
> https://github.com/SELinuxProject/refpolicy/wiki/HowToContribute
>
> But I need to update it, as I prefer the GitHub pull requests these days
> (though will always accept patches via the list). I'll add a
> CONTRIBUTING file, though it will probably consist mostly of the above link.
I indeed missed the wiki page, which is now easier to find. Thanks!
Nicolas
prev parent reply other threads:[~2019-01-10 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 7:51 [PATCH] systemd related interfaces Russell Coker
2019-01-05 19:18 ` Chris PeBenito
2019-01-05 21:39 ` Nicolas Iooss
2019-01-05 21:49 ` Dominick Grift
2019-01-06 18:39 ` Chris PeBenito
2019-01-06 22:10 ` Nicolas Iooss
2019-01-07 23:36 ` Chris PeBenito
2019-01-10 23:10 ` Nicolas Iooss [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='CAJfZ7=nDEFBe+amDqAhnrOoaWcK=82kLz=BQeBuoMZqPpfxnvw@mail.gmail.com' \
--to=nicolas.iooss@m4x.org \
--cc=dac.override@gmail.com \
--cc=pebenito@ieee.org \
--cc=russell@coker.com.au \
--cc=selinux-refpolicy@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).