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

Re: "git checkout" safety feature

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 5, 2018, 01:12 UTC
Message-ID
<xmqqk1lsl448.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<6afef19d-08f6-9cce-a491-3a49808c57ec@urlichs.de>
Matthias Urlichs <matthias@urlichs.de> writes:
Show 6 quoted lines
> A recent discussion on LWN https://lwn.net/Articles/770642/ noted that
> "git checkout <release> <file…>" does not warn if one if the files has
> been modified locally, nor is there an option to do so.
>
> IMHO that should be fixed, preferably by somebody who knows git's
> internals well enough to do so in half an hour ;-)

"git checkout <commit> <pathspec>" is a feature to overwrite local changes. It is what you use when you make a mess editing the files and want to go back to a known state. Why should that feature be destroyed?

Previous: Matthias UrlichsNext: Matthias Urlichs
Message 2 of 5 in “"git checkout" safety feature”
  1. Matthias UrlichsNov 4, 2018
  2. Junio C HamanoNov 5, 2018
  3. Matthias UrlichsNov 5, 2018
  4. Jeff KingNov 5, 2018
  5. Duy NguyenNov 5, 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.