From: "Martin Ågren" <martin.agren@gmail.com>
To: git@vger.kernel.org
Cc: Chris Torek <chris.torek@gmail.com>
Subject: [PATCH 0/2] git-diff.txt: reorder possible usages
Date: Mon, 13 Jul 2020 21:10:07 +0200 [thread overview]
Message-ID: <cover.1594666410.git.martin.agren@gmail.com> (raw)
Going through the doc-diff between v2.27.0 and v2.28.0-rc0, I only
noticed some small things related to b7e10b2ca2 ("Documentation: usage
for diff combined commits", 2020-06-12). The first issue might not be
something a lot of people would stumble on, but the second one could
probably trip someone up.
All feedback welcome.
Martin
Martin Ågren (2):
git-diff.txt: don't mark required argument as optional
git-diff.txt: reorder possible usages
Documentation/git-diff.txt | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
--
2.28.0.rc0
next reply other threads:[~2020-07-13 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 19:10 Martin Ågren [this message]
2020-07-13 19:10 ` [PATCH 1/2] git-diff.txt: don't mark required argument as optional Martin Ågren
2020-07-13 19:45 ` Junio C Hamano
2020-07-13 19:10 ` [PATCH 2/2] git-diff.txt: reorder possible usages Martin Ågren
2020-07-13 22:04 ` Chris Torek
2020-07-14 14:49 ` Martin Ågren
2020-07-15 2:45 ` 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=cover.1594666410.git.martin.agren@gmail.com \
--to=martin.agren@gmail.com \
--cc=chris.torek@gmail.com \
--cc=git@vger.kernel.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.