From: Duy Nguyen <pclouds@gmail.com>
Date: Sat, 08 Dec 2018 17:28:09 GMT
Subject: Re: why doesn't "git reset" mention optional pathspec?
Message-ID: <CACsJy8APyyAWM+L=HU1XM4V+qdTWqjto6x=Q06By8DbgtYfpCA@mail.gmail.com>
In-Reply-To: <alpine.LFD.2.21.1812081103500.29142@localhost.localdomain>

On Sat, Dec 8, 2018 at 5:08 PM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
>
>   from "man git-reset":
>
> SYNOPSIS
>   git reset [-q] [<tree-ish>] [--] <paths>...
>   git reset (--patch | -p) [<tree-ish>] [--] [<paths>...]
>   git reset [--soft | --mixed [-N] | --hard | --merge | --keep] [-q] [<commit>]
>
> oddly, the third form says nothing about possible "<paths>", even
> though i'm pretty sure they're valid in that third case (at least for
> "--mixed"). thoughts? is that just an oversight in the man page?

--mixed prints a deprecation warning. I don't think it's worth making
the synopsis more complicated for that. All other modes reject
pathspec.
-- 
Duy