From: "Pooyan Khanjankhani via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Pooyan Khanjankhani <pooyankhan@gmail.com>,
Pooyan Khanjankhani <p.khanjankhani@digikala.com>
Subject: [PATCH] revisions.txt: correct a mistake in dotted range notations section
Date: Wed, 26 Apr 2023 07:44:41 +0000 [thread overview]
Message-ID: <pull.1485.git.git.1682495081131.gitgitgadget@gmail.com> (raw)
From: Pooyan Khanjankhani <p.khanjankhani@digikala.com>
Insert a missing 'not' word in a negative sentence.
... but are [not] reachable from neither A or C.
Signed-off-by: Pooyan Khanjankhani <p.khanjankhani@digikala.com>
---
docs: Fix sentencing
Just fixed a sentence in docs.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1485%2FTheKhanj%2Fdocs%2Fsentencing-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1485/TheKhanj/docs/sentencing-v1
Pull-Request: https://github.com/git/git/pull/1485
Documentation/revisions.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt
index 9aa58052bc7..00c2f030da5 100644
--- a/Documentation/revisions.txt
+++ b/Documentation/revisions.txt
@@ -306,7 +306,7 @@ other, e.g.
does *not* specify two revision ranges for most commands. Instead
it will name a single connected set of commits, i.e. those that are
-reachable from either B or D but are reachable from neither A or C.
+reachable from either B or D but are not reachable from neither A or C.
In a linear history like this:
---A---B---o---o---C---D
base-commit: ae73b2c8f1da39c39335ee76a0f95857712c22a7
--
gitgitgadget
next reply other threads:[~2023-04-26 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 7:44 Pooyan Khanjankhani via GitGitGadget [this message]
2023-04-26 16:46 ` [PATCH] revisions.txt: correct a mistake in dotted range notations section Junio C Hamano
2023-04-26 21:16 ` Chris Torek
2023-05-02 16:57 ` Felipe Contreras
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.1485.git.git.1682495081131.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=p.khanjankhani@digikala.com \
--cc=pooyankhan@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.