Re: why is git destructive by default? (i suggest it not be!)

From: Jakub Narebski <jnareb@gmail.com>
Date: Jun 24, 2008, 19:08 UTC
Message-ID: <m31w2mlki4.fsf@localhost.localdomain>
In-Reply-To: <48612CB0.2070303@panasas.com>

Boaz Harrosh <bharrosh@panasas.com> writes:

> Sorry
> git-reset --clean -f/-n for removing local changes
> git reset --hard for moving HEAD on a clean tree only

Wouldn't "git reset <commit-ish>" be enough then? It modifies where current branch points to (as opposed to git-checkout modifying what is the current branch), and it modifies index. What it doesn't modify is working directory, but it is clean already.

So the solution is: don't use `--hard'.

-- 
Jakub Narebski
Poland
ShadeHawk on #git

$ 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.