Re: [PATCH] doc: fix location of index in worktree scenatio
- From
Andreas Heiduk <asheiduk@gmail.com>
- Date
- Jun 10, 2017, 17:24 UTC
- Message-ID
- <d2b21102-eb32-7061-14ee-aa8906fe9eeb@gmail.com>
- In-Reply-To
- <xmqqmv9g1487.fsf@gitster.mtv.corp.google.com>
Am 10.06.2017 um 13:17 schrieb Junio C Hamano:
Show 5 quoted lines
> Andreas Heiduk <asheiduk@gmail.com> writes: > >> When setting `.gitattributes` in a second worktree, a plain `rm .git/index` >> does not actually delete the index. >>
[...]
Show 7 quoted lines
> Right. > > I however have to wonder if we can do the same without futzing > directly with the "index" file as a filesystem entity. With or > without your update, what is taught in the document feels like > munging a disk block with binary editor to correct a corrupted > filesystem X-<.
IMO `rm .git/index` is like munging a disk block WITHOUT a binary editor but with plain `dd seek=... skip=... count=...`, `hexdump`, `ed` and back - every step is clear in principle but painful and dangerous. :-)
> For example, can we do this "empty the index" step with things like > > $ git rm --cached .
That would be `git rm --cached -rq .`?
Executing this in the git repo gives me an index file with 2.1kb. I don't know whether or not this index still contains something relevant for this case.
Show 5 quoted lines
> or > > $ git read-tree --empty > > instead?
Nice! The `index` file contains 46 bytes.
For me THAT one is like a nice binary editor apt for the job :-) I'll queue that.