From: "Monika Kairaitytė via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: "Monika Kairaitytė" <monika@kibit.lt>,
"Monika Kairaityte" <monika@kibit.lt>
Subject: [PATCH] documentation: add missing word "ref"
Date: Sun, 29 Sep 2024 15:17:07 +0000 [thread overview]
Message-ID: <pull.1803.git.1727623027242.gitgitgadget@gmail.com> (raw)
From: Monika Kairaityte <monika@kibit.lt>
In the git-fetch documentation, description of <refspec> syntax is not
entirely clear. When explaining about "the destination ref <dst>", word
"ref" is included. Logically, it should be the same in the explanation
of "the source <src>".
Signed-off-by: Monika Kairaityte <monika@kibit.lt>
---
documentation: add missing word "ref"
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1803%2Fmokibit%2Fdocs-add-missing-ref-word-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1803/mokibit/docs-add-missing-ref-word-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1803
Documentation/pull-fetch-param.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/pull-fetch-param.txt b/Documentation/pull-fetch-param.txt
index c718f7946f0..066a35af9cd 100644
--- a/Documentation/pull-fetch-param.txt
+++ b/Documentation/pull-fetch-param.txt
@@ -24,7 +24,7 @@ ifdef::git-pull[]
endif::git-pull[]
+
The format of a <refspec> parameter is an optional plus
-`+`, followed by the source <src>, followed
+`+`, followed by the source ref <src>, followed
by a colon `:`, followed by the destination ref <dst>.
The colon can be omitted when <dst> is empty. <src> is
typically a ref, but it can also be a fully spelled hex object
base-commit: 3857aae53f3633b7de63ad640737c657387ae0c6
--
gitgitgadget
next reply other threads:[~2024-09-29 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 15:17 Monika Kairaitytė via GitGitGadget [this message]
2024-10-01 18:36 ` [PATCH] documentation: add missing word "ref" Junio C Hamano
2024-10-09 19:38 ` Monika Kairaityte
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.1803.git.1727623027242.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=monika@kibit.lt \
/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.