From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Sverre Rabbelier <srabbelier@gmail.com>
Subject: [RFC PATCH 0/2] SubmittingPatches: What to base work on
Date: Mon, 19 Apr 2010 01:23:11 +0530 [thread overview]
Message-ID: <1271620352-sup-4304@kytes> (raw)
This is a two-part series. The first patch is a verbatim copy of
Junio's rough draft [1]. The second patch is my rewrite, which I
intend to squash into the first.
[1] http://article.gmane.org/gmane.comp.version-control.git/144378/
Ramkumar Ramachandra (2):
SubmittingPatches: Add new section about what to base work on
SubmittingPatches: Complete rewrite of section 0
Documentation/SubmittingPatches | 49 ++++++++++++++++++++++++++++++--------
1 files changed, 38 insertions(+), 11 deletions(-)
next reply other threads:[~2010-04-18 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 19:53 Ramkumar Ramachandra [this message]
2010-04-18 23:11 ` [RFC PATCH 0/2] SubmittingPatches: What to base work on 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=1271620352-sup-4304@kytes \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=srabbelier@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).