From: Eric Paris <eparis@redhat.com>
To: selinux@tycho.nsa.gov
Subject: Incoming flood of updates to SELinux userspace
Date: Wed, 20 Jul 2011 15:53:46 -0400 [thread overview]
Message-ID: <4E27324A.50309@redhat.com> (raw)
I decided to take on as a personal challenge the effort of trying to get
everything that Fedora and Red Hat have done with SELinux userspace into
the upstream trees. My process has been to try to pick apart the
gigantic patch that Fedora carries and break that into reasonable size
patches with descriptive and meaningful changelogs. As I'm breaking
them up I'm also attempting to review them for appropriateness of
inclusion. As I find that patches that I either think are wrong, or I
can't explain, or whatever, I'm also committing those to my tree, but
trying to make sure it is clear that is the case. I would quickly like
to switch Fedora to using my tree as its 'upstream' instead of the
Tresys tree. Remember, my tree is going to contain everything in
Fedora, even if I don't think it's a good idea or ready to be merged
with the real upstream tree.
I've asked Dan (and everyone) to start reviewing patches in my tree a
couple per day. He is going to send an e-mail to this list stating that
he believes a patch is ready to commit. If both Dan and I agree that
the patch in question is appropriate for upstream I will commit it to
the real upstream repo. As I commit patches upstream every day I will
rebase my private tree. My private tree is NOT stable.
If you would like to participate, PLEASE DO! Reviewing patches is easy!
All you have to do is:
git clone http://oss.tresys.com/git/selinux.git selinux-userspace
cd selinux-userspace
edit .git/config and add:
[remote "eparis"]
fetch = +refs/heads/*:refs/remotes/eparis/*
url = git://git.infradead.org/users/eparis/selinux-userspace.git
git remote update
git format-patch -o /tmp/patches/ origin/master..eparis/master
I'd suggest that every day you wish to review you run:
rm -rf /tmp/patches
git remote update
git format-patch -o /tmp/patches/ origin/master..eparis/master
Because my repo will be constantly rebasing and changing as I push
patches into the upstream repo.
If you have ever posted a patch for SELinux userspace and you don't find
it in my tree, in my mind it's lost forever. Please resend it. Just
because I put it in my tree doesn't mean it's going to go upstream, but
if I don't put it in my private tracking tree, we can rest assured it's
not headed that way!
Please let me know if anyone has any problems, thoughts, concerns,
issues, or comments about how I'm doing things!
-Eric
--
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 reply other threads:[~2011-07-20 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 19:53 Eric Paris [this message]
2011-07-26 16:08 ` Incoming flood of updates to SELinux userspace - Missing patch Richard Haines
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=4E27324A.50309@redhat.com \
--to=eparis@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.