public inbox for eudev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: eudev@lists.gentoo.org
Cc: Marcus Folkesson <marcus.folkesson@gmail.com>
Subject: [eudev] [PATCH] CONTRIBUTION: give instruction on how to send patches to mailinglist
Date: Tue, 28 Nov 2017 11:49:24 +0100	[thread overview]
Message-ID: <20171128104924.8598-1-marcus.folkesson@gmail.com> (raw)

For all those who prefer emails instead of web GUIs.

Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
---
 CONTRIBUTING | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 71a82f6c4..81d343137 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -108,7 +108,7 @@ doing
 Then push it to your public repo.
 
 
-4. Open an issue at
+4.a Open an issue at (using GitHub)
 
 	https://github.com/gentoo/eudev/issues?state=open
 
@@ -116,6 +116,14 @@ And request a pull of your clean commit.  A team member will review it,
 discuss it and commit it to master or reject it.
 
 
+4.b Send to mailing list (using git format-patch)
+Make sure you are subscribe on the mailing list. If you do not, send an email to
+	eudev+subscribe@lists.gentoo.org
+and follow instructions.
+
+When sending patches to mailing list, use
+	git send-email --to eudev@lists.gentoo.org 0001-foo-bar.patch
+
 5. eudev is a peer-reviewed project.  So even team members must ask another
 team member to sign-off and commit your work.  The only exception are trivial
 commits
-- 
2.13.1



             reply	other threads:[~2017-11-28 10:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 10:49 Marcus Folkesson [this message]
2017-11-29 11:24 ` [eudev] [PATCH] CONTRIBUTION: give instruction on how to send patches to mailinglist Anthony G. Basile

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=20171128104924.8598-1-marcus.folkesson@gmail.com \
    --to=marcus.folkesson@gmail.com \
    --cc=eudev@lists.gentoo.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