From: Eric Paris <eparis@parisplace.org>
To: Paul Moore <pmoore@redhat.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: [PATCH] selinux: add Paul Moore as a SELinux maintainer
Date: Wed, 18 Sep 2013 14:09:36 -0400 [thread overview]
Message-ID: <1379527776.3032.56.camel@localhost> (raw)
In-Reply-To: <13288872.e4rikYWUTT@sifl>
On Wed, 2013-09-18 at 14:05 -0400, Paul Moore wrote:
> I believe everything should be fixed now, take a look and if I've messed
> something up again, let me know.
You used merge instead of rebase, but either way is fine. Send an
e-mail to sfr@canb.auug.org and ask him to pull your tree (be sure to
tell him which branch) and to drop my tree. It should also go to
linux-next@vger.kernel.org and cc me.
--
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:[~2013-09-18 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 17:14 [PATCH] selinux: add Paul Moore as a SELinux maintainer Paul Moore
2013-09-18 17:22 ` Eric Paris
2013-09-18 18:05 ` Paul Moore
2013-09-18 18:09 ` Eric Paris [this message]
2013-09-18 18:12 ` Paul Moore
2013-09-24 1:47 ` James Morris
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=1379527776.3032.56.camel@localhost \
--to=eparis@parisplace.org \
--cc=pmoore@redhat.com \
--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.