Re: [PATCH] revisions.txt: correct a mistake in dotted range notations section

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Pooyan Khanjankhani via GitGitGadget" <gitgitgadget@xxxxxxxxx>
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




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux