From: Anselm Schüler <mail@anselmschueler.com>
Date: Tue, 16 Sep 2025 20:34:39 GMT
Subject: Re: Why does git-status suggest different commands to unstage files depending on whether there is a commit yet or not?
Message-ID: <de49d686-73fa-4bb9-9ec6-b65d5432a30a@anselmschueler.com>
In-Reply-To: <5036f7d8-8ac9-4f50-99af-5a3a2d1a07fc@anselmschueler.com>

Sorry for that. I apologise for the messed-up formatting. Let’s try that 
again.

—

After a new repository has been created, before a commit has been made, 
when files are staged, git-status suggests using git-rm to unstage files:

$ git status
[...]
No commits yet

Changes to be committed:
    (use "git rm --cached <file>..." to unstage)
[...]

After a commit has been made, git-status suggests using git-restore instead:

$ git status
[...]
Changes to be committed:
    (use "git restore --staged <file>..." to unstage)
[...]

Why is this the case?