On Wed, Oct 04, 2017 at 11:26:55AM -0500, Robert Dailey wrote: > On Tue, Oct 3, 2017 at 9:00 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > > Torsten Bögershausen <tboegi@xxxxxx> writes: > > > >>> $ git rm -r --cached . && git add . > >> > >> (Both should work) > >> > >> To be honest, from the documentation, I can't figure out the difference between > >> $ git read-tree --empty > >> and > >> $ git rm -r --cached . > >> > >> Does anybody remember the discussion, why we ended up with read-tree ? > > > > We used to use neither, and considered it fine to "rm .git/index" if > > you wanted to empty the on-disk index file in the old world. In the > > modern world, folks want you to avoid touching filesystem directly > > and instead want you to use Git tools, and the above are two obvious > > ways to do so. > > > > "git read-tree" (without any parameter, i.e. "read these 0 trees and > > populate the index with it") and its modern and preferred synonym > > "git read-tree --empty" (i.e. "I am giving 0 trees and I know the > > sole effect of this command is to empty the index.") are more direct > > ways to express "I want the index emptied" between the two. > > > > The other one, "git rm -r --cached .", in the end gives you the same > > state because it tells Git to "iterate over all the entries in the > > index, find the ones that match pathspec '.', and remove them from > > the index.". It is not wrong per-se, but conceptually it is a bit > > roundabout way to say that "I want the index emptied", I would > > think. > > > > I wouldn't be surprised if the "rm -r --cached ." were a lot slower, > > due to the overhead of having to do the pathspec filtering that ends > > up to be a no-op, but there shouldn't be a difference in the end > > result. > > You guys are obviously worlds ahead of me on the internals of things, > but from my perspective I like to avoid the "plumbing" commands as > much as I can. Even if I used them, if I have to tell the rest of my > team "this is the way to do it", they're going to give me dirty looks > if I ask them to run things like this that make no sense to them. > That's the argument I have to deal with when it comes to Git's > usability within the team I manage. So based on this, I'd favor the > `git rm -r --cached` approach because this is the more common result > you see in Google, and also makes a little more sense from a high > level of thought perspective. However, this is just my personal > opinion. `read-tree --empty` is far less self explanatory IMHO. > > Also let's not forget the second part of the command chain that > results in the different behavior. In one case, I use `git add` which > results in proper line ending normalization. In the other case, I do > `git reset --hard` which does *NOT* result in the line endings > normalized (`git status` shows no results). In both cases, I'm still > doing `git rm -r --cached`, so I am doubtful that is the root cause > for the line ending normalization piece. I'm still trying to > understand why both give different results (root cause) and also get > an understanding of what the correct (modern) solution is for line > ending normalization (not necessarily which is the right way to > clear/delete the index, which is really AFAIK just a means to this end > and an implementation detail of sorts for this specific task). Hopefully I am able to give a useful answer. "git reset --hard" works like a hammer and may destroy work that has been done, in our case the cleaning of the index, which is needed for normalization since Git 2.10 (or so) Back to the question: One solution, which you can tell your team, is this one: $ git rm -r --cached . && git add . And as Junio pointed out, this may be slower than needed. And we don't want "slow" solutions in the official documentation ;-) Whatever you find on search engines may get stale after a while, so that we appreciate direct questions here. (And I will open an issue on Github the next days) The background is that the CRLF handling in Git changed over the years, and one effect is that "git reset" is not "allowed" any more. For the interested reader: https://github.com/git-for-windows/git/issues/954
