git/run-command.c, branch v2.28.1Mirror of https://git.kernel.org/pub/scm/git/git.git/
https://www.git.shady.money/git/atom?h=v2.28.12021-02-12T14:50:09ZSync with 2.27.12021-02-12T14:50:09ZJohannes Schindelinjohannes.schindelin@gmx.de2021-02-12T14:50:09Zurn:sha1:3f01e56686b2fd08d919306717764391409ac81e
* maint-2.27:
Git 2.27.1
Git 2.26.3
Git 2.25.5
Git 2.24.4
Git 2.23.4
Git 2.22.5
Git 2.21.4
Git 2.20.5
Git 2.19.6
Git 2.18.5
Git 2.17.6
unpack_trees(): start with a fresh lstat cache
run-command: invalidate lstat cache after a command finished
checkout: fix bug that makes checkout follow symlinks in leading path
Sync with 2.26.32021-02-12T14:50:04ZJohannes Schindelinjohannes.schindelin@gmx.de2021-02-12T14:50:04Zurn:sha1:2d1142a3e8455af1bdab2cb19dfaf428cdc03459
* maint-2.26:
Git 2.26.3
Git 2.25.5
Git 2.24.4
Git 2.23.4
Git 2.22.5
Git 2.21.4
Git 2.20.5
Git 2.19.6
Git 2.18.5
Git 2.17.6
unpack_trees(): start with a fresh lstat cache
run-command: invalidate lstat cache after a command finished
checkout: fix bug that makes checkout follow symlinks in leading path
Sync with 2.24.42021-02-12T14:49:55ZJohannes Schindelinjohannes.schindelin@gmx.de2021-02-12T14:49:55Zurn:sha1:97d1dcb1efb2899a40b42da894f2ead0eb7af7ef
* maint-2.24:
Git 2.24.4
Git 2.23.4
Git 2.22.5
Git 2.21.4
Git 2.20.5
Git 2.19.6
Git 2.18.5
Git 2.17.6
unpack_trees(): start with a fresh lstat cache
run-command: invalidate lstat cache after a command finished
checkout: fix bug that makes checkout follow symlinks in leading path
Sync with 2.21.42021-02-12T14:49:41ZJohannes Schindelinjohannes.schindelin@gmx.de2021-02-12T14:49:41Zurn:sha1:bcf08f33d840b8a6bef347aea3ac2359874c888a
* maint-2.21:
Git 2.21.4
Git 2.20.5
Git 2.19.6
Git 2.18.5
Git 2.17.6
unpack_trees(): start with a fresh lstat cache
run-command: invalidate lstat cache after a command finished
checkout: fix bug that makes checkout follow symlinks in leading path
Sync with 2.19.62021-02-12T14:49:17ZJohannes Schindelinjohannes.schindelin@gmx.de2021-02-12T14:49:17Zurn:sha1:804963848e325ff6f4213e53aeda6ef831574e48
* maint-2.19:
Git 2.19.6
Git 2.18.5
Git 2.17.6
unpack_trees(): start with a fresh lstat cache
run-command: invalidate lstat cache after a command finished
checkout: fix bug that makes checkout follow symlinks in leading path
Sync with 2.18.52021-02-12T14:47:47ZJohannes Schindelinjohannes.schindelin@gmx.de2021-02-12T14:47:47Zurn:sha1:fb049fd85b298d386dca2e0bcf74a1f52a7b2038
* maint-2.18:
Git 2.18.5
Git 2.17.6
unpack_trees(): start with a fresh lstat cache
run-command: invalidate lstat cache after a command finished
checkout: fix bug that makes checkout follow symlinks in leading path
Sync with 2.17.62021-02-12T14:47:42ZJohannes Schindelinjohannes.schindelin@gmx.de2021-02-12T14:47:42Zurn:sha1:9b77cec89b64f0910df911952ccee0cdf0046f48
* maint-2.17:
Git 2.17.6
unpack_trees(): start with a fresh lstat cache
run-command: invalidate lstat cache after a command finished
checkout: fix bug that makes checkout follow symlinks in leading path
run-command: invalidate lstat cache after a command finished2021-02-12T14:47:02ZJohannes Schindelinjohannes.schindelin@gmx.de2021-02-02T21:09:52Zurn:sha1:0d58fef58a6f382ba1d35f47a01cb55d8976335f
In the previous commit, we intercepted calls to `rmdir()` to invalidate
the lstat cache in the successful case, so that the lstat cache could
not have the idea that a directory exists where there is none.
The same situation can arise, of course, when a separate process is
spawned (most notably, this is the case in `submodule_move_head()`).
Obviously, we cannot know whether a directory was removed in that
process, therefore we must invalidate the lstat cache afterwards.
Note: in contrast to `lstat_cache_aware_rmdir()`, we invalidate the
lstat cache even in case of an error: the process might have removed a
directory and still have failed afterwards.
Co-authored-by: Matheus Tavares <matheus.bernardino@usp.br>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Merge branch 'ta/wait-on-aliased-commands-upon-signal' into master2020-07-15T23:29:43ZJunio C Hamanogitster@pobox.com2020-07-15T23:29:43Zurn:sha1:05920f041a57ac9ee86a8615cfca414450e65365
When an aliased command, whose output is piped to a pager by git,
gets killed by a signal, the pager got into a funny state, which
has been corrected (again).
* ta/wait-on-aliased-commands-upon-signal:
Wait for child on signal death for aliases to externals
Wait for child on signal death for aliases to builtins
Wait for child on signal death for aliases to builtins2020-07-07T20:14:05ZTrygve Aabergetrygveaa@gmail.com2020-07-07T12:17:14Zurn:sha1:e662df7e830a9d93ca36b74a7b5e670e139b0da1
When you hit ^C all the processes in the tree receives it. When a git
command uses a pager, git ignores this and waits until the pager quits.
However, when using an alias there is an additional process in the tree
which didn't ignore the signal. That caused it to exit which in turn
caused the pager to exit. This fixes that for aliases to builtins.
This was originally fixed in 46df6906 (execv_dashed_external: wait
for child on signal death, 2017-01-06), but was broken by ee4512ed
(trace2: create new combined trace facility, 2019-02-22) and then
b9140840 (git: avoid calling aliased builtins via their dashed form,
2019-07-29).
Signed-off-by: Trygve Aaberge <trygveaa@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>