All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Pooyan Khanjankhani via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Pooyan Khanjankhani <pooyankhan@gmail.com>,
	Pooyan Khanjankhani <p.khanjankhani@digikala.com>
Subject: Re: [PATCH] revisions.txt: correct a mistake in dotted range notations section
Date: Wed, 26 Apr 2023 09:46:10 -0700	[thread overview]
Message-ID: <xmqqo7natwvh.fsf@gitster.g> (raw)
In-Reply-To: <pull.1485.git.git.1682495081131.gitgitgadget@gmail.com> (Pooyan Khanjankhani via GitGitGadget's message of "Wed, 26 Apr 2023 07:44:41 +0000")

"Pooyan Khanjankhani via GitGitGadget" <gitgitgadget@gmail.com>
writes:

>      $ git log A..B C..D
>
>  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
>
> because A and B are reachable from C, the revision range specified
> by these two dotted ranges is a single commit D.

Isn't that an unwanted double negative?

The first hit I got about "neither double negation" on Google search
was:

https://www.grammar-monster.com/lessons/either_or_neither_nor_double_negative.htm

but the source of this might sound more authoritative:

https://dictionary.cambridge.org/grammar/british-grammar/neither-neither-nor-and-not-either_2


  reply	other threads:[~2023-04-26 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26  7:44 [PATCH] revisions.txt: correct a mistake in dotted range notations section Pooyan Khanjankhani via GitGitGadget
2023-04-26 16:46 ` Junio C Hamano [this message]
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=xmqqo7natwvh.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --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.