From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: why doesn't "git reset" mention optional pathspec?
Date: Sun, 09 Dec 2018 10:42:20 +0900 [thread overview]
Message-ID: <xmqqftv75vcz.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CACsJy8A_vaVUt389O5ABa+vsrVDgo1L3WZzVx+P0qfiaY9=p1w@mail.gmail.com> (Duy Nguyen's message of "Sat, 8 Dec 2018 19:17:28 +0100")
Duy Nguyen <pclouds@gmail.com> writes:
> Without --mixed, you're using the first form
>
> git reset [-q] [<tree-ish>] [--] <paths>...
>
> which accepts pathspec. If it's not clear, of course patches are welcome.
Yup. The deprecation is about spelling with "--mixed" when invoking
the "restore these paths out of tree-ish (or HEAD when omitted)
only in the index" mode. The feature is of course not deprecated
(but it might have been better if it were "git checkout --cached").
next prev parent reply other threads:[~2018-12-09 1:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 16:05 why doesn't "git reset" mention optional pathspec? Robert P. J. Day
2018-12-08 17:28 ` Duy Nguyen
2018-12-08 17:32 ` Robert P. J. Day
2018-12-08 17:34 ` Duy Nguyen
2018-12-08 17:37 ` Robert P. J. Day
2018-12-08 18:17 ` Duy Nguyen
2018-12-09 1:42 ` Junio C Hamano [this message]
2018-12-08 17:42 ` Robert P. J. Day
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=xmqqftv75vcz.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=rpjday@crashcourse.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).