All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Lawrence <slawrence@tresys.com>
To: SELinux <selinux@tycho.nsa.gov>
Subject: Patch Review Process
Date: Mon, 9 May 2011 11:14:32 -0400	[thread overview]
Message-ID: <4DC804D8.1080605@tresys.com> (raw)

Recently, I've not been merging patches at the rate that I would like.
The delay is a problem itself, but it has also meant that people aren't
certain of the status of the patches that have been submitted.

I understand that this can be frustrating. Not only am I going to work
harder to review and merge patches in a more timely manner, but also at
providing better feedback more quickly. As such, I will make some simple
changes.

First, I will either quickly respond with a review, or reply with a
confirmation that I received the patch and it has been added to our
queue. Second, I will send out bi-weekly emails to the list detailing
which patches have been reviewed, which patches I am currently working
on, and the updated patch queue.

While these changes are relatively minor, I think they should help to
make the review process more transparent and less frustrating. To start
this off, the current patch queue is at the bottom of this email. If you
don't see a patch that you have submitted, or you have an updated
version, please send the patch to this mailing list and I'll update the
queue.

For anyone wishing to submit a patch, the process remains the same:
- Make sure the patch applies to the current HEAD of the git repo
(http://oss.tresys.com/git/selinux.git).
- Send it to this list using the Linux kernel submission standards
(http://www.kernel.org/doc/Documentation/SubmittingPatches). Note: using
git format-patch and git send-email will take care of most of this for you.
- I will shortly respond with a confirmation

Finally, if anyone has any suggestions on ways to make the patch review
process better, my ears are all open.


Current Patch Queue:

checkpolicy: fix filename identifier
http://marc.info/?l=selinux&m=130442985211760&w=2

selabel_open fix processing of substitution files (update)
http://marc.info/?l=selinux&m=130314146920796&w=2

selinux_file_context_verify function returns wrong value
http://marc.info/?l=selinux&m=129968866831934&w=2

Fix boolean handling in semanage
http://marc.info/?l=selinux&m=125433524126271&w=2

Add modules support to semanage
http://marc.info/?l=selinux&m=125433587727297&w=2

sandbox changes
http://marc.info/?l=selinux&m=129226611027331&w=2

libselinux mountpoint changing
http://marc.info/?l=selinux&m=130444622801373&w=2

Add note to checkmodule man page about versions
http://marc.info/?l=selinux&m=127913558418720&w=2

Bug in restorecond for the first user logged in
http://marc.info/?t=128164314700001&r=1&w=2

transactions in semanage man page
http://marc.info/?l=selinux&m=127959379422398&w=2

libsemanage python3 support
http://marc.info/?l=selinux&m=128025784525867&w=2

libselinux python3 support
http://marc.info/?l=selinux&m=129226509225674&w=2

SETools patch: adding exclude type feature in queries
http://marc.info/?l=selinux&m=128448149528834&w=2

Move newrole to file caps/libcapng
http://marc.info/?l=selinux&m=129226621227513&w=2

Improve semodule performance
http://marc.info/?l=selinux&m=128043503603540&w=2

Fix warning messages generated by GCC 4.6
http://marc.info/?l=selinux&m=127845525722194&w=2

sepolgen kernel policy version check
http://marc.info/?l=selinux&m=128948444127169&w=2

Remove DEFAULTUSER handling from get_context_list
http://marc.info/?l=selinux&m=129226509425687&w=2

sepolgen current patch from Fedora
http://marc.info/?l=selinux&m=129226551726416&w=2

Improved error message for load_policy
http://marc.info/?l=selinux&m=129226567426640&w=2

Semanage patch
http://marc.info/?l=selinux&m=129233335310866&w=2

restorecond: Ignore IN_IGNORED inotify events
http://marc.info/?l=selinux&m=125380417916233&w=2

setfiles/restorecond patch
http://marc.info/?l=selinux&m=129226589026919&w=2

policycoreutils:  update audit2allow manpage
http://marc.info/?l=selinux&m=129304945226866&w=2

libsemanage: include MCS/MLS level when generating files_contexts.homedirs
http://marc.info/?l=selinux&m=129421658323663&w=2

setfiles: provide an option to avoid abortion on a missing file
http://marc.info/?l=selinux&m=129819885027010&w=2

minor improvements and clean-ups for setfiles
http://marc.info/?l=selinux&m=129819262321520&w=2

policycoreutils scripts updates
http://marc.info/?l=selinux&m=129226648427897&w=2

Fix options for policycoreutils binaries
http://marc.info/?l=selinux&m=125718355929168&w=2


--
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:[~2011-05-09 16:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 15:14 Steve Lawrence [this message]
2011-05-09 19:21 ` Patch Review Process Guido Trentalancia
2011-05-09 19:58   ` Steve Lawrence
2011-05-13  7:53     ` Patch Review Process - Missing patch for selinux_set_mapping Richard Haines
2011-05-13  9:28     ` Patch Review Process Kohei Kaigai
2011-05-13 10:34       ` Guido Trentalancia
2011-05-16 14:30       ` Steve Lawrence
2011-05-16 15:15         ` Kohei Kaigai
2011-05-16 16:04         ` Greg Smith
2011-05-18 13:31           ` Steve Lawrence
2011-05-09 19:38 ` 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=4DC804D8.1080605@tresys.com \
    --to=slawrence@tresys.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.