git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jim Meyering <jim@meyering.net>,
	Drew Northup <drew.northup@maine.edu>,
	git list <git@vger.kernel.org>, Yann Dirson <ydirson@altern.org>,
	Stephen Boyd <bebarino@gmail.com>
Subject: [PATCH/RFC v3 0/5] Documentation/format-patch: more hints on submitting patches
Date: Thu, 14 Apr 2011 21:11:00 -0500	[thread overview]
Message-ID: <20110415021100.GA19829@elie> (raw)
In-Reply-To: <7vlizcfpz8.fsf@alter.siamese.dyndns.org>

Junio C Hamano wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:

>> -linkgit:git-am[1], linkgit:git-send-email[1]
>> +linkgit:git-am[1], linkgit:git-send-email[1], linkgit:git-imap-send[1],
>> +Documentation/SubmittingPatches
>
> Hmm, I suspect this is (1) bad because the end users without the source
> may not have access to it, and (2) bad because it may indicate that there
> are hints and tricks in SubmittingPatches file, which narrowly targets
> developers of this project, but they would also be helpful to the general
> audience.  Perhaps some text needs moving from there to here?

Yep, true.  How about this?

Patch 1 explains the "canonical" and "with scissors" formats of mails
with patches.  It's basically the same as before, except with lots of
nice suggestions from Junio incorporated.

Patch 2 explains how new patch submitters can test their tools before
unleashing them on the world.  It should be common sense, but...  The
text is taken from Documentation/SubmittingPatches.

Patch 3 is rough; it exposes the Thunderbird MUA-specific hints.  Help
making it accurate and consistent with git-imap-send(1) would be very
much appreciated

Patch 4 contains KMail hints from SubmittingPatches; help would
appreciated in making sure that's still accurate, too.

Patch 5 contains the famous GMail hints, finally spreading them out
in EXAMPLES sections where they belong.

Maybe this can be a good starting point for future changes.

Jonathan Nieder (5):
  Documentation: describe the format of messages with inline patches
  Documentation: explain how to check for patch corruption
  Documentation: hints for sending patches inline with Thunderbird
  Documentation: publicize KMail hints for sending patches inline
  Documentation: publicize hints for sending patches with GMail

 Documentation/SubmittingPatches    |  207 +++-------------------------------
 Documentation/git-format-patch.txt |  217 ++++++++++++++++++++++++++++++++++++
 Documentation/git-imap-send.txt    |   29 +++++
 Documentation/git-send-email.txt   |   19 +++-
 4 files changed, 277 insertions(+), 195 deletions(-)

  reply	other threads:[~2011-04-15  2:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 15:39 [PATCH] remove doubled words, e.g., s/to to/to/, and fix related typos Jim Meyering
2011-04-13 18:35 ` Drew Northup
2011-04-13 21:22   ` Jim Meyering
2011-04-13 22:17     ` [PATCH/RFC] Documentation/format-patch: summarize patch-sending workflow Jonathan Nieder
2011-04-13 22:38       ` Junio C Hamano
2011-04-14 21:11         ` [PATCH v2] Documentation: summarize how format-patch output is consumed Jonathan Nieder
2011-04-14 22:05           ` Junio C Hamano
2011-04-15  2:11             ` Jonathan Nieder [this message]
2011-04-15  2:22               ` [PATCH 1/5] Documentation: describe the format of messages with inline patches Jonathan Nieder
2011-04-15 20:11                 ` Drew Northup
2011-04-15 20:24                   ` Junio C Hamano
2011-04-15  2:24               ` [PATCH 2/5] Documentation: explain how to check for patch corruption Jonathan Nieder
2011-04-15  4:53                 ` Junio C Hamano
2011-04-15  6:17                   ` Jonathan Nieder
2011-04-15  2:28               ` [PATCH 3/5] Documentation: hints for sending patches inline with Thunderbird Jonathan Nieder
2011-04-15  2:32               ` [PATCH 4/5] Documentation: publicize KMail hints for sending patches inline Jonathan Nieder
2011-04-17 13:57                 ` Michele Ballabio
2011-04-15  2:33               ` [PATCH 5/5] Documentation: publicize hints for sending patches with GMail Jonathan Nieder
2011-04-15  7:41               ` [PATCH/RFC 6/5] Documentation/format-patch: suggest Toggle Word Wrap add-on for Thunderbird Johannes Sixt
2011-04-15 17:54                 ` Junio C Hamano
2011-04-15 18:01                   ` Michael J Gruber
2011-04-15 18:49                     ` Junio C Hamano
2011-04-15 20:17                     ` Jonathan Nieder
2011-04-18  6:31                   ` [PATCH 6/5 v2] " Johannes Sixt
2011-04-13 22:26     ` [PATCH] remove doubled words, e.g., s/to to/to/, and fix related typos Jakub Narebski
2011-04-13 18:47 ` 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=20110415021100.GA19829@elie \
    --to=jrnieder@gmail.com \
    --cc=bebarino@gmail.com \
    --cc=drew.northup@maine.edu \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jim@meyering.net \
    --cc=ydirson@altern.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;
as well as URLs for NNTP newsgroup(s).