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

Re: [BUG?] git checkout $commit -- somedir doesn't drop files

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 17, 2013, 19:58 UTC
Message-ID
<xmqqeh8nxltc.fsf@gitster.dls.corp.google.com>
In-Reply-To
<20130917190659.GA15588@pengutronix.de>
Uwe Kleine-König  <u.kleine-koenig@pengutronix.de> writes:
Show 27 quoted lines
> after these commands:
>
> 	$ git init
> 	$ mkdir subdir
> 	$ echo a > subdir/a
> 	$ git add subdir/a
> 	$ git commit -m a
> 	$ echo more a >> subdir/a
> 	$ echo b > subdir/b
> 	$ git add subdir/*
> 	$ git commit -m b
> 	$ git checkout HEAD^ -- subdir
>
> I'd expect that subdir/b is removed from the index as this file didn't
> exist in HEAD^ but git-status only reports:
>
> 	# On branch master
> 	# Changes to be committed:
> 	#   (use "git reset HEAD <file>..." to unstage)
> 	#
> 	#	modified:   subdir/a
> 	#
>
> Is this intended?
>
> (I'm using git 1.8.4.rc3 as shipped by Debian (package version
> 1:1.8.4~rc3-1).)

The intended behaviour of "git checkout tree-ish -- pathspec" has always been "grab paths that match pathspec from tree-ish, add them to the index and check them out to the working tree". If you have subdir/b in the index and the working tree, it will be kept when the paths that match "subdir" pathspec is grabbed out of the tree-ish HEAD^ (namely, subdir/a) is added to the index and to the working tree.

I could argue that the above intended behaviour is suboptimal and it should have been "the resulting paths in the index and the work tree that match the given pathspec must be identical to that of the tree-ish". In the resulting index or working tree, paths that match "subdir" pathspec in the above result is subdir/a and subdir/b, and that is different from what exists in the given tree-ish (which has only subdir/a and not subdir/b), and under that modified definition, what the current one does is not correct.

I vaguely recall arguing for the updated behaviour described in the above paragraph, and I even might have started working on it, but I do not think we changed this behaviour recently, unfortunately.

Previous: Uwe Kleine-KönigNext: Jeff King
Message 2 of 15 in “[BUG?] git checkout $commit -- somedir doesn't drop files”
  1. Uwe Kleine-KönigSep 17, 2013
  2. Junio C HamanoSep 17, 2013
  3. Jeff KingSep 17, 2013
  4. Junio C HamanoSep 17, 2013
  5. Jeff KingSep 17, 2013
  6. Junio C HamanoSep 17, 2013
  7. Jeff KingSep 17, 2013
  8. Junio C HamanoSep 17, 2013
  9. Jeff KingSep 17, 2013
  10. Junio C HamanoSep 17, 2013
  11. Jeff KingSep 19, 2013
  12. Junio C HamanoSep 19, 2013
  13. Jeff KingSep 19, 2013
  14. Junio C HamanoSep 20, 2013
  15. Jeff KingSep 17, 2013

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.