From: aranea@aixah.de (Luis Ressel)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] ANN: Reference Policy moved to GitHub
Date: Thu, 26 Jun 2014 22:07:04 +0200 [thread overview]
Message-ID: <20140626220704.6194100a@gentp.lnet> (raw)
In-Reply-To: <5395CAA0.4010900@tresys.com>
Dear Maintainers,
I see you've incorporated commits from an Github pull request for the
first time [1]. I personally think this could be problematic, as there
hasn't been any announcement/discussion of these commits on the mailing
list.
Could you please clear up your opinion towards pull requests - whether
they will be accepted or not and whether mailing list patch submission
or pull-requests are prefered.
I personally would propose that pull requests should be either
1) disallowed, so that patch submission is only possible on the ML
(This approach is also taken by Git itself and by Linux, to name
prominent examples) or
2) allowed, but with the requirement that the patches or at least an
announcement is also posted on the ML.
Of course, the last paragraph represents my personal opinion and I'm
very interested how the maintainers and the other contributors think
about it.
[1] https://github.com/TresysTechnology/refpolicy/pull/1
Regards,
Luis Ressel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 966 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20140626/2e6f5c63/attachment.bin
next prev parent reply other threads:[~2014-06-26 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 14:54 ANN: Reference Policy moved to GitHub Christopher J. PeBenito
2014-06-09 14:54 ` [refpolicy] " Christopher J. PeBenito
2014-06-14 1:46 ` Russell Coker
2014-06-14 1:46 ` [refpolicy] " Russell Coker
2014-06-14 7:20 ` Elia Pinto
2014-06-14 7:20 ` Elia Pinto
2014-06-14 14:43 ` Russell Coker
2014-06-14 14:43 ` Russell Coker
2014-06-26 20:07 ` Luis Ressel [this message]
2014-06-27 14:45 ` Christopher J. PeBenito
2014-06-27 17:56 ` Luis Ressel
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=20140626220704.6194100a@gentp.lnet \
--to=aranea@aixah.de \
--cc=refpolicy@oss.tresys.com \
/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.