Browse Source
This has the same effect as --no-replace-objects option; git ignores the replace refs. When --no-replace-objects option is passed to git, this environment variable is set to "1" and exported to subprocesses in order to propagate the same setting. It is useful for example for scripts, as the git commands used in them can now be aware that they must not read replace refs. Tested-by: Michael J Gruber <git@drmicha.warpmail.net> Signed-off-by: Christian Couder <chriscool@tuxfamily.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>maint
![chriscool@tuxfamily.org](/assets/img/avatar_default.png)
![Junio C Hamano](/assets/img/avatar_default.png)
5 changed files with 24 additions and 0 deletions
Loading…
Reference in new issue