From: "Martin Ågren" <martin.agren@gmail.com>
To: git@vger.kernel.org
Cc: Teng Long <dyroneteng@gmail.com>,
Sean Allred <allred.sean@gmail.com>,
Patrick Steinhardt <ps@pks.im>
Subject: [PATCH 0/4] some doc fixes on v2.42.0-rc2
Date: Wed, 16 Aug 2023 16:24:32 +0200 [thread overview]
Message-ID: <cover.1692194193.git.martin.agren@gmail.com> (raw)
Looking into the changes to our documentation from v2.41.0 up to
v2.42.0-rc2, I found some improvements we could make. I've cc'd the
original authors on this cover letter and the respective patches.
I realize we're fairly late in the release cycle. The impact of these
patches is small, which could mean they're "low risk" or "low benefit"
depending on how you want to look at it.
Martin
Martin Ågren (4):
notes doc: split up run-on sentences
notes doc: tidy up `--no-stripspace` paragraph
show-ref doc: fix carets in monospace
rev-list-options: fix typo in `--stdin` documentation
Documentation/git-notes.txt | 15 +++++++--------
Documentation/git-show-ref.txt | 4 ++--
Documentation/rev-list-options.txt | 2 +-
3 files changed, 10 insertions(+), 11 deletions(-)
--
2.42.0.rc2.215.g538df5cf27
next reply other threads:[~2023-08-16 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 14:24 Martin Ågren [this message]
2023-08-16 14:24 ` [PATCH 1/4] notes doc: split up run-on sentences Martin Ågren
2023-08-17 2:22 ` Teng Long
2023-08-16 14:24 ` [PATCH 2/4] notes doc: tidy up `--no-stripspace` paragraph Martin Ågren
2023-08-17 2:52 ` Teng Long
2023-08-17 6:52 ` Martin Ågren
2023-08-16 14:24 ` [PATCH 3/4] show-ref doc: fix carets in monospace Martin Ågren
2023-08-16 14:24 ` [PATCH 4/4] rev-list-options: fix typo in `--stdin` documentation Martin Ågren
2023-08-16 18:41 ` Junio C Hamano
2023-08-16 18:52 ` Junio C Hamano
2023-08-17 6:51 ` Martin Ågren
2023-08-16 18:35 ` [PATCH 0/4] some doc fixes on v2.42.0-rc2 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.1692194193.git.martin.agren@gmail.com \
--to=martin.agren@gmail.com \
--cc=allred.sean@gmail.com \
--cc=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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).