From: kristofferhaugsbakk@fastmail.com
To: git@vger.kernel.org
Cc: "Kristoffer Haugsbakk" <code@khaugsbakk.name>,
"Jean-Noël Avila" <jn.avila@free.fr>,
"Karthik Nayak" <karthik.188@gmail.com>
Subject: [PATCH 2/2] doc: branch: fix inline-verbatim
Date: Sat, 3 May 2025 21:13:09 +0200 [thread overview]
Message-ID: <2e41f0f0f0738418375f77146e4b10e0e562d7fb.1746299135.git.code@khaugsbakk.name> (raw)
In-Reply-To: <cover.1746299135.git.code@khaugsbakk.name>
From: Kristoffer Haugsbakk <code@khaugsbakk.name>
7b399322a2e (doc: apply new format to git-branch man page, 2025-03-19)
updated the formatting for this doc to, among other things, use backtick
for some elements. In the process `è` was used by accident instead
of backtick.
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
Documentation/git-branch.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-branch.adoc b/Documentation/git-branch.adoc
index 50a1e13e1f2..c0afddc424d 100644
--- a/Documentation/git-branch.adoc
+++ b/Documentation/git-branch.adoc
@@ -373,7 +373,7 @@ $ git branch -D test <2>
------------
+
<1> Delete the remote-tracking branches "todo", "html" and "man". The next
- `git fetch` or `git pullè will create them again unless you configure them not to.
+ `git fetch` or `git pull` will create them again unless you configure them not to.
See linkgit:git-fetch[1].
<2> Delete the "test" branch even if the "master" branch (or whichever branch
is currently checked out) does not have all commits from the test branch.
--
2.49.0.459.gf65182a99e5
next prev parent reply other threads:[~2025-05-03 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 19:13 [PATCH 0/2] doc: fix subheading and inline-verbatim kristofferhaugsbakk
2025-05-03 19:13 ` [PATCH 1/2] doc: reflog: fix `drop` subheading kristofferhaugsbakk
2025-05-03 19:13 ` kristofferhaugsbakk [this message]
2025-05-06 13:01 ` [PATCH 2/2] doc: branch: fix inline-verbatim Jean-Noël Avila
2025-05-05 17:47 ` [PATCH 0/2] doc: fix subheading and inline-verbatim 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=2e41f0f0f0738418375f77146e4b10e0e562d7fb.1746299135.git.code@khaugsbakk.name \
--to=kristofferhaugsbakk@fastmail.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
--cc=karthik.188@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 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).