All of lore.kernel.org
 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: Re: [PATCH 2/5] Documentation: explain how to check for patch corruption
Date: Fri, 15 Apr 2011 01:17:58 -0500	[thread overview]
Message-ID: <20110415061758.GA20441@elie> (raw)
In-Reply-To: <7vsjtkdsij.fsf@alter.siamese.dyndns.org>

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

>> +++ b/Documentation/SubmittingPatches
[...]
>> +While you are at it, check the resulting commit log message from
>> +a trial run of applying the patch.  If what is in the resulting
[...]
> Perhaps the last paragraph can also go, as a copy of it now is in git-am(1)?

Yes, good idea.  I wanted to keep a reminder to look over the
resulting commit (and especially its log message), but this section is
definitely not the place.

>> +++ b/Documentation/git-format-patch.txt
>> @@ -286,6 +286,52 @@ title is likely to be different from the subject
>> +One way to test if your MUA is set up correctly is:
>> +
>> +* Send the patch to yourself, exactly the way you would, except
>> +  with To: and Cc: lines that do not contain the list and
>> +  maintainer address.
>
> ... "except for removing other people from To: and Cc: lines to avoid
> spamming them with your test"?

Yes, that is much clearer.  If you'd like, I can collect other
corrections and read it over again myself to resend tomorrow.

  reply	other threads:[~2011-04-15  6:18 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             ` [PATCH/RFC v3 0/5] Documentation/format-patch: more hints on submitting patches Jonathan Nieder
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 [this message]
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=20110415061758.GA20441@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 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.