Commit 6701fc6
committed
fetch/pull: use the sparse index
The 'git fetch' and 'git pull' commands somehow read the index. In the
case of 'git pull', much of the reason is that the HEAD might change due
to the update from the remote. It is unclear why 'git fetch' needs it.
However, I was able to measure time in ensure_full_index() because these
commands do parse an index.
Signed-off-by: Derrick Stolee <dstolee@microsoft.com>1 parent dd53e79 commit 6701fc6
2 files changed
Lines changed: 4 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1987 | 1987 | | |
1988 | 1988 | | |
1989 | 1989 | | |
| 1990 | + | |
| 1991 | + | |
1990 | 1992 | | |
1991 | 1993 | | |
1992 | 1994 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
954 | 954 | | |
955 | 955 | | |
956 | 956 | | |
| 957 | + | |
| 958 | + | |
957 | 959 | | |
958 | 960 | | |
959 | 961 | | |
| |||
0 commit comments