From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Richard Haines <richard_c_haines@btinternet.com>,
SELinux-NSA <SELinux@tycho.nsa.gov>,
linux-sctp@vger.kernel.org, Paul Moore <paul@paul-moore.com>
Subject: Re: github issue trackers
Date: Fri, 18 Nov 2016 17:24:03 +0000 [thread overview]
Message-ID: <20161118172402.GC24936@localhost.localdomain> (raw)
In-Reply-To: <b54fe273-01bf-e128-0dcc-5fb764f865f8@tycho.nsa.gov>
On Fri, Nov 18, 2016 at 12:02:33PM -0500, Stephen Smalley wrote:
> On 11/18/2016 11:49 AM, Richard Haines wrote:
> > On Fri, 2016-11-18 at 10:30 -0500, Stephen Smalley wrote:
> >> Hi,
> >>
> >> I've populated the github issue trackers for the selinux (userspace)
> >> and
> >> selinux-kernel github projects, see:
> >> https://github.com/SELinuxProject/selinux/issues
> >> and
> >> https://github.com/SELinuxProject/selinux-kernel/issues
> >>
> >> The old ToDo wiki pages are being migrated over, although I would
> >> like
> >> to drop items that are either a) already in progress, b)
> >> vague/ill-defined, or c) unlikely to be done. Going forward, we'll
> >> just
> >> use the issue trackers for all new items.
> >>
> >> Feel free to identify additional issues that I may have missed, but
> >> please try to keep them well-defined and feasible.
> >
> > Just thought I would update you regarding the status of the RFC SCTP
> > kernel patches I sent a few years ago that are referenced at:
> > https://github.com/SELinuxProject/selinux-kernel/issues/5
> >
> > I have been keeping these updated and fixing problems as I find them,
> > however I have not resubmitted. If there is interest I'm happy to
> > submit again and see how far I can get. If anyone is interested
> > I keep a set of patches at:
> > http://arctic.selinuxproject.org/~rhaines/selinux-sctp
> >
> > For the gory details read:
> > http://arctic.selinuxproject.org/~rhaines/selinux-sctp/readme.txt
>
> Thanks, I'd certainly like to see them upstreamed. Were there specific
> objections or just a lack of response?
+1
Thanks,
Marcelo
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Richard Haines <richard_c_haines@btinternet.com>,
SELinux-NSA <SELinux@tycho.nsa.gov>,
linux-sctp@vger.kernel.org, Paul Moore <paul@paul-moore.com>
Subject: Re: github issue trackers
Date: Fri, 18 Nov 2016 15:24:03 -0200 [thread overview]
Message-ID: <20161118172402.GC24936@localhost.localdomain> (raw)
In-Reply-To: <b54fe273-01bf-e128-0dcc-5fb764f865f8@tycho.nsa.gov>
On Fri, Nov 18, 2016 at 12:02:33PM -0500, Stephen Smalley wrote:
> On 11/18/2016 11:49 AM, Richard Haines wrote:
> > On Fri, 2016-11-18 at 10:30 -0500, Stephen Smalley wrote:
> >> Hi,
> >>
> >> I've populated the github issue trackers for the selinux (userspace)
> >> and
> >> selinux-kernel github projects, see:
> >> https://github.com/SELinuxProject/selinux/issues
> >> and
> >> https://github.com/SELinuxProject/selinux-kernel/issues
> >>
> >> The old ToDo wiki pages are being migrated over, although I would
> >> like
> >> to drop items that are either a) already in progress, b)
> >> vague/ill-defined, or c) unlikely to be done. Going forward, we'll
> >> just
> >> use the issue trackers for all new items.
> >>
> >> Feel free to identify additional issues that I may have missed, but
> >> please try to keep them well-defined and feasible.
> >
> > Just thought I would update you regarding the status of the RFC SCTP
> > kernel patches I sent a few years ago that are referenced at:
> > https://github.com/SELinuxProject/selinux-kernel/issues/5
> >
> > I have been keeping these updated and fixing problems as I find them,
> > however I have not resubmitted. If there is interest I'm happy to
> > submit again and see how far I can get. If anyone is interested
> > I keep a set of patches at:
> > http://arctic.selinuxproject.org/~rhaines/selinux-sctp
> >
> > For the gory details read:
> > http://arctic.selinuxproject.org/~rhaines/selinux-sctp/readme.txt
>
> Thanks, I'd certainly like to see them upstreamed. Were there specific
> objections or just a lack of response?
+1
Thanks,
Marcelo
next prev parent reply other threads:[~2016-11-18 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 15:30 github issue trackers Stephen Smalley
2016-11-18 16:49 ` Richard Haines
2016-11-18 17:02 ` Stephen Smalley
2016-11-18 17:02 ` Stephen Smalley
2016-11-18 17:24 ` Marcelo Ricardo Leitner [this message]
2016-11-18 17:24 ` Marcelo Ricardo Leitner
2016-11-18 18:00 ` Paul Moore
2016-11-18 18:00 ` Paul Moore
2016-11-22 15:35 ` Richard Haines
2016-11-22 15:35 ` Richard Haines
2016-11-18 17:58 ` Paul Moore
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=20161118172402.GC24936@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=SELinux@tycho.nsa.gov \
--cc=linux-sctp@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=richard_c_haines@btinternet.com \
--cc=sds@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.