doc: remove the mailing list

Ever since the move to GH, the mailing list hasn't been very useful
or very popular so let's just drop it.

Signed-off-by: Paul Moore <paul@paul-moore.com>
Signed-off-by: Tom Hromatka <tom.hromatka@oracle.com>

1 files changed, 5 insertions, 44 deletions

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 7130b90..350d370 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -113,47 +113,8 @@ your real name, saying:
 
 You can add this to your commit description in `git` with `git commit -s`
 
-## Post Your Patches Upstream
-
-The libseccomp project accepts both GitHub pull requests and patches sent via
-the mailing list.  GitHub pull requests are preferred.  This sections below
-explain how to contribute via either method. Please read each step and perform
-all steps that apply to your chosen contribution method.
-
-### Submitting via Email
-
-Depending on how you decided to work with the libseccomp code base and what
-tools you are using there are different ways to generate your patch(es).
-However, regardless of what tools you use, you should always generate your
-patches using the "unified" diff/patch format and the patches should always
-apply to the libseccomp source tree using the following command from the top
-directory of the libseccomp sources:
-
-	# patch -p1 < changes.patch
-
-If you are not using git, stacked git (stgit), or some other tool which can
-generate patch files for you automatically, you may find the following command
-helpful in generating patches, where "libseccomp.orig/" is the unmodified
-source code directory and "libseccomp/" is the source code directory with your
-changes:
-
-	# diff -purN libseccomp.orig/ libseccomp/
-
-When in doubt please generate your patch and try applying it to an unmodified
-copy of the libseccomp sources; if it fails for you, it will fail for the rest
-of us.
-
-Finally, you will need to email your patches to the mailing list so they can
-be reviewed and potentially merged into the main libseccomp repository.  When
-sending patches to the mailing list it is important to send your email in text
-form, no HTML mail please, and ensure that your email client does not mangle
-your patches.  It should be possible to save your raw email to disk and apply
-it directly to the libseccomp source code; if that fails then you likely have
-a problem with your email client.  When in doubt try a test first by sending
-yourself an email with your patch and attempting to apply the emailed patch to
-the libseccomp repository; if it fails for you, it will fail for the rest of
-us trying to test your patch and include it in the main libseccomp repository.
-
-### Submitting via GitHub
-
-See [this guide](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request) if you've never done this before.
+## Post Your Patches to GitHub
+
+The libseccomp project accepts new patches via GitHub pull requests, if you
+are not familiar with GitHub pull requests please see
+[this guide](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request).