From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Jason Holden <jason.k.holden.swdev@gmail.com>
Subject: [PATCH 1/3] SubmittingPatches: who am I and who cares?
Date: Tue, 1 Jan 2013 15:24:53 -0800 [thread overview]
Message-ID: <1357082695-29713-2-git-send-email-gitster@pobox.com> (raw)
In-Reply-To: <1357082695-29713-1-git-send-email-gitster@pobox.com>
The introductory text in the "long version" talks about the origin
of this document with "I started ...", but it is unclear who that I
is, and more importantly, it is not interesting how it was started.
Just state the purpose of the document to help readers decide if it
is releavant to them.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
Documentation/SubmittingPatches | 10 ++--------
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index c34c9d1..b9fd182 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -60,14 +60,8 @@ Checklist (and a short version for the impatient):
Long version:
-I started reading over the SubmittingPatches document for Linux
-kernel, primarily because I wanted to have a document similar to
-it for the core GIT to make sure people understand what they are
-doing when they write "Signed-off-by" line.
-
-But the patch submission requirements are a lot more relaxed
-here on the technical/contents front, because the core GIT is
-thousand times smaller ;-). So here is only the relevant bits.
+Here are some guidelines for people who want to contribute their code
+to this software.
(0) Decide what to base your work on.
--
1.8.1.209.gc32ab23
next prev parent reply other threads:[~2013-01-01 23:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 23:24 [PATCH 0/3] Update SubmittingPatches Junio C Hamano
2013-01-01 23:24 ` Junio C Hamano [this message]
2013-01-01 23:24 ` [PATCH 2/3] SubmittingPatches: mention subsystems with dedicated repositories Junio C Hamano
2013-01-02 1:52 ` Jason Holden
2013-01-02 2:14 ` Junio C Hamano
2013-01-02 17:22 ` Junio C Hamano
2013-01-04 20:58 ` [PATCH] SubmittingPatches: Document how to request a patch review tag Jason Holden
2013-01-04 21:47 ` Junio C Hamano
2013-01-06 7:32 ` Michael Haggerty
2013-01-06 9:01 ` Junio C Hamano
2013-01-01 23:24 ` [PATCH 3/3] SubmittingPatches: remove overlong checklist Junio C Hamano
2013-01-02 9:08 ` [PATCH 0/3] Update SubmittingPatches Jeff King
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=1357082695-29713-2-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jason.k.holden.swdev@gmail.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 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).