{"thread":{"id":"53546","subject":"Bug: \"git restore --staged\" on a newly created repository","startedAt":"2020-05-26T06:28:46Z","lastAt":"2020-05-27T07:32:07Z","messageCount":2,"participants":["Xirui Zhao","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"398571","messageId":"1F3FD418-38D2-4A10-A882-666D4327F993@gmail.com","threadId":"53546","inReplyTo":null,"subject":"Bug: \"git restore --staged\" on a newly created repository","fromName":"Xirui Zhao","fromEmail":"zhaoxirui434@gmail.com","sentAt":"2020-05-26T06:18:34Z","receivedAt":"2020-05-26T06:28:46Z","isPatch":false,"sender":{"key":"zhaoxirui434@gmail.com","avatar":null},"body":"Tested on git version 2.27.0-rc1 (latest build from master branch on github) and 2.26.2\n`git restore --staged file` on a newly created repository outputs error \"fatal: could not resolve HEAD\", but `git reset file` correctly unstages the file."},{"id":"398616","messageId":"20200527073205.GC4006199@coredump.intra.peff.net","threadId":"53546","inReplyTo":"1F3FD418-38D2-4A10-A882-666D4327F993@gmail.com","subject":"Re: Bug: \"git restore --staged\" on a newly created repository","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2020-05-27T07:32:05Z","receivedAt":"2020-05-27T07:32:07Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, May 26, 2020 at 02:18:34PM +0800, Xirui Zhao wrote:\n\n> Tested on git version 2.27.0-rc1 (latest build from master branch on github) and 2.26.2\n> `git restore --staged file` on a newly created repository outputs\n> error \"fatal: could not resolve HEAD\", but `git reset file` correctly\n> unstages the file.\n\nYeah, \"restore\" is based on git-checkout, which is a little pickier than\n\"git reset\" here. I don't think this ever worked in any version of\ngit-restore. It would probably be OK for it to use the empty tree when\nHEAD is unborn, at least when operating in git-restore mode.\n\n-Peff\n"}]}