git, branch v2.34.3Fork of git SCM with my patches.http://git.kilabit.info/git/atom?h=v2.34.32022-04-13T22:21:31ZGit 2.34.32022-04-13T22:21:31ZJunio C Hamanogitster@pobox.com2022-04-13T22:21:31Zurn:sha1:2f0dde7852b7866bb044926f73334ff3fc30654b
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Git 2.33.32022-04-13T22:21:28ZJunio C Hamanogitster@pobox.com2022-04-13T22:21:28Zurn:sha1:1f65dd6ae635f77c588ac432cad1a299723d00d6
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Git 2.32.22022-04-13T22:21:26ZJunio C Hamanogitster@pobox.com2022-04-13T22:21:26Zurn:sha1:15304344342b7c888f732d28f908890d874bcb0c
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Git 2.31.32022-04-13T22:21:08ZJunio C Hamanogitster@pobox.com2022-04-13T22:21:08Zurn:sha1:09f66d65f87e0a547c186e4027368a826a965256
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Git 2.30.42022-04-13T20:31:29ZJunio C Hamanogitster@pobox.com2022-04-13T20:31:29Zurn:sha1:17083c79ae842b51d82518e2efe5281346acea0e
Signed-off-by: Junio C Hamano <gitster@pobox.com>
setup: opt-out of check with safe.directory=*2022-04-13T19:42:51ZDerrick Stoleederrickstolee@github.com2022-04-13T15:32:31Zurn:sha1:0f85c4a30b072a26d74af8bbf63cc8f6a5dfc1b8
With the addition of the safe.directory in 8959555ce
(setup_git_directory(): add an owner check for the top-level directory,
2022-03-02) released in v2.35.2, we are receiving feedback from a
variety of users about the feature.
Some users have a very large list of shared repositories and find it
cumbersome to add this config for every one of them.
In a more difficult case, certain workflows involve running Git commands
within containers. The container boundary prevents any global or system
config from communicating `safe.directory` values from the host into the
container. Further, the container almost always runs as a different user
than the owner of the directory in the host.
To simplify the reactions necessary for these users, extend the
definition of the safe.directory config value to include a possible '*'
value. This value implies that all directories are safe, providing a
single setting to opt-out of this protection.
Note that an empty assignment of safe.directory clears all previous
values, and this is already the case with the "if (!value || !*value)"
condition.
Signed-off-by: Derrick Stolee <derrickstolee@github.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
setup: fix safe.directory key not being checked2022-04-13T19:42:51ZMatheus Valadaresme@m28.io2022-04-13T15:32:30Zurn:sha1:bb50ec3cc300eeff3aba7a2bea145aabdb477d31
It seems that nothing is ever checking to make sure the safe directories
in the configs actually have the key safe.directory, so some unrelated
config that has a value with a certain directory would also make it a
safe directory.
Signed-off-by: Matheus Valadares <me@m28.io>
Signed-off-by: Derrick Stolee <derrickstolee@github.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t0033: add tests for safe.directory2022-04-13T19:42:49ZDerrick Stoleederrickstolee@github.com2022-04-13T15:32:29Zurn:sha1:e47363e5a8bdf5144059d664c45c0975243ef05b
It is difficult to change the ownership on a directory in our test
suite, so insert a new GIT_TEST_ASSUME_DIFFERENT_OWNER environment
variable to trick Git into thinking we are in a differently-owned
directory. This allows us to test that the config is parsed correctly.
Signed-off-by: Derrick Stolee <derrickstolee@github.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Git 2.34.22022-03-23T23:31:36ZJohannes Schindelinjohannes.schindelin@gmx.de2022-03-17T09:57:52Zurn:sha1:4d0b43aa765a0056c88381eea862364c95e358ca
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Sync with 2.33.22022-03-23T23:31:36ZJohannes Schindelinjohannes.schindelin@gmx.de2022-03-17T09:57:50Zurn:sha1:93fbff09eb8ed9e728a61623a15a53a46a762639
* maint-2.33:
Git 2.33.2
Git 2.32.1
Git 2.31.2
GIT-VERSION-GEN: bump to v2.33.1
Git 2.30.3
setup_git_directory(): add an owner check for the top-level directory
Add a function to determine whether a path is owned by the current user