selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: William Roberts <bill.c.roberts@gmail.com>
Cc: SElinux list <selinux@vger.kernel.org>
Subject: Re: PR 193 sitting for uClibC fix
Date: Thu, 26 Mar 2020 12:45:08 -0400	[thread overview]
Message-ID: <CAEjxPJ4iQmgz0Po7o1REc5Fb63ci=6WtF8=e6zwD46=1o9x9SQ@mail.gmail.com> (raw)
In-Reply-To: <CAFftDdr=2ji0=dG2Jc2A=rTcu215ETkeEkBxnp3UMeXzp=VRkA@mail.gmail.com>

On Thu, Mar 26, 2020 at 12:22 PM William Roberts
<bill.c.roberts@gmail.com> wrote:
>
> This PR:
> https://github.com/SELinuxProject/selinux/pull/193
>
> Has been sitting forever. I looked through the mailing list and didn't
> see any patches hit the list,
> we should either close it, or merge it.
>
> Thoughts? If we need it to hit the list, can I grab it and sign-off on
> it and post it?

You can't sign-off on someone else's patch without them first signing off on it
or otherwise certifying to you that it falls under clauses (a), (b),
or (c) of the DCO.
You could create your own patch to achieve the same end, especially
since this one is trivial and seems
to be modeled after an existing commit,
ab0e27003ef245f20512d1808b1dfee662ab8f41, so it
seems like it is relatively safe.

  reply	other threads:[~2020-03-26 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 16:21 PR 193 sitting for uClibC fix William Roberts
2020-03-26 16:45 ` Stephen Smalley [this message]
2020-03-26 16:46   ` William Roberts
2020-03-26 16:52     ` Stephen Smalley
2020-03-26 16:58       ` Stephen Smalley
2020-03-26 17:02         ` William Roberts

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='CAEjxPJ4iQmgz0Po7o1REc5Fb63ci=6WtF8=e6zwD46=1o9x9SQ@mail.gmail.com' \
    --to=stephen.smalley.work@gmail.com \
    --cc=bill.c.roberts@gmail.com \
    --cc=selinux@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).