From: Jari Aalto <jari.aalto@cante.net>
To: git@vger.kernel.org
Subject: [PATCH] Checklist clarifications: added "Commits", "Patch:" headings
Date: Mon, 30 Apr 2007 14:04:03 +0300 [thread overview]
Message-ID: <r6q2xgws.fsf@cante.net> (raw)
Added email address and message 'Send your patch to...'
Signed-off-by: Jari Aalto <jari.aalto@cante.net>
---
Documentation/SubmittingPatches | 9 ++++++++-
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 2386f49..238d410 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -1,5 +1,7 @@
Checklist (and a short version for the impatient):
+ Commits:
+
- make commits of logical units
- check for unnecessary whitespace with "git diff --check"
before committing
@@ -12,8 +14,13 @@ Checklist (and a short version for the impatient):
commit message (or just use the option "-s" when
committing) to confirm that you agree to the Developer's
Certificate of Origin
+
+ Patch:
+
+ - send your patch to <git@vger.kernel.org> by using
+ git-format-patch(1) with option "-M". See also
+ git-send-email(1).
- do not PGP sign your patch
- - use "git format-patch -M" to create the patch
- do not attach your patch, but read in the mail
body, unless you cannot teach your mailer to
leave the formatting of the patch alone.
--
1.5.1.2.GIT
next reply other threads:[~2007-04-30 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 11:04 Jari Aalto [this message]
2007-04-30 11:36 ` [PATCH] Checklist clarifications: added "Commits", "Patch:" headings Johannes Schindelin
2007-04-30 12:02 ` Jari Aalto
2007-04-30 12:09 ` Julian Phillips
2007-04-30 12:42 ` Johannes Schindelin
2007-04-30 16:04 ` [PATCH] v2: " Jari Aalto
2007-04-30 23:35 ` Junio C Hamano
2007-04-30 21:00 ` [PATCH] send-email: add a few config variables Junio C Hamano
2007-05-01 4:11 ` [PATCH] Checklist clarifications: added "Commits", "Patch:" headings Junio C Hamano
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=r6q2xgws.fsf@cante.net \
--to=jari.aalto@cante.net \
--cc=git@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 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.