From: "Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Philippe Blain <levraiphilippeblain@gmail.com>
Subject: [PATCH 0/3] Fix a few documentation errors around the raw diff output
Date: Mon, 13 Jun 2022 12:29:40 +0000 [thread overview]
Message-ID: <pull.1259.git.1655123383.gitgitgadget@gmail.com> (raw)
Here are a few doc fixes for some things that I noticed out while reading
the man pages for 'git diff-files' and 'git diff-index'. These are quite
old!
Philippe Blain (3):
diff-format.txt: fix ancient copy-paste error
diff-format.txt: correct misleading wording
diff-index.txt: update raw output format in examples
Documentation/diff-format.txt | 6 +++---
Documentation/git-diff-index.txt | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
base-commit: 5699ec1b0aec51b9e9ba5a2785f65970c5a95d84
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1259%2Fphil-blain%2Fdiff-files-doc-fixes-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1259/phil-blain/diff-files-doc-fixes-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1259
--
gitgitgadget
next reply other threads:[~2022-06-13 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 12:29 Philippe Blain via GitGitGadget [this message]
2022-06-13 12:29 ` [PATCH 1/3] diff-format.txt: fix ancient copy-paste error Philippe Blain via GitGitGadget
2022-06-13 18:23 ` Junio C Hamano
2022-06-13 18:26 ` Junio C Hamano
2022-06-14 12:20 ` Philippe Blain
2022-06-13 12:29 ` [PATCH 2/3] diff-format.txt: correct misleading wording Philippe Blain via GitGitGadget
2022-06-13 18:56 ` Junio C Hamano
2022-06-14 12:31 ` Philippe Blain
2022-06-13 12:29 ` [PATCH 3/3] diff-index.txt: update raw output format in examples Philippe Blain via GitGitGadget
2022-06-13 18:59 ` Junio C Hamano
2022-06-13 18:15 ` [PATCH 0/3] Fix a few documentation errors around the raw diff output 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=pull.1259.git.1655123383.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=levraiphilippeblain@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 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.