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

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

From
Robert P. J. Day <rpjday@crashcourse.ca>
Date
Dec 8, 2018, 16:05 UTC
Message-ID
<alpine.LFD.2.21.1812081103500.29142@localhost.localdomain>
  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?

rday
-- 
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                  http://crashcourse.ca/dokuwiki

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
Next: Duy Nguyen
Message 1 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.