git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: why doesn't "git reset" mention optional pathspec?

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 9, 2018, 01:42 UTC
Message-ID
<xmqqftv75vcz.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<CACsJy8A_vaVUt389O5ABa+vsrVDgo1L3WZzVx+P0qfiaY9=p1w@mail.gmail.com>
Duy Nguyen <pclouds@gmail.com> writes:
Show 5 quoted lines
> 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").

Previous: Duy NguyenNext: Robert P. J. Day
Message 7 of 8 in “why doesn't "git reset" mention optional pathspec?”
  1. Robert P. J. DayDec 8, 2018
  2. Duy NguyenDec 8, 2018
  3. Robert P. J. DayDec 8, 2018
  4. Duy NguyenDec 8, 2018
  5. Robert P. J. DayDec 8, 2018
  6. Duy NguyenDec 8, 2018
  7. Junio C HamanoDec 9, 2018
  8. Robert P. J. DayDec 8, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.