From: Jeff King <peff@peff.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] commit: fixup misplacement of --no-post-rewrite description
Date: Fri, 2 Nov 2012 09:22:59 -0400 [thread overview]
Message-ID: <20121102132259.GD2598@sigill.intra.peff.net> (raw)
In-Reply-To: <m2hap88a2g.fsf@igel.home>
On Fri, Nov 02, 2012 at 01:26:47PM +0100, Andreas Schwab wrote:
> In e858af6 (commit: document a couple of options) the description of the
> --no-post-rewrite option was put inside the paragraph for the --amend
> option. Move it down after the paragraph.
>
> Signed-off-by: Andreas Schwab <schwab@linux-m68k.org>
Thanks, the modified output looks much more sane.
-Peff
prev parent reply other threads:[~2012-11-02 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 12:26 [PATCH] commit: fixup misplacement of --no-post-rewrite description Andreas Schwab
2012-11-02 13:22 ` Jeff King [this message]
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=20121102132259.GD2598@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=schwab@linux-m68k.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).