Re: [PATCH] git: add --no-optional-locks option
- From
Johannes Sixt <j6t@kdbg.org>
- Date
- Sep 21, 2017, 18:25 UTC
- Message-ID
- <7a2d895c-df8c-1305-234f-7f8e2b271ec2@kdbg.org>
- In-Reply-To
- <20170921043214.pyhdsrpy4omy54rm@sigill.intra.peff.net>
Am 21.09.2017 um 06:32 schrieb Jeff King:
Show 27 quoted lines
> diff --git a/Documentation/git.txt b/Documentation/git.txt > index 6e3a6767e5..8dd3ae05ae 100644 > --- a/Documentation/git.txt > +++ b/Documentation/git.txt > @@ -159,6 +159,10 @@ foo.bar= ...`) sets `foo.bar` to the empty string which ` git config > Add "icase" magic to all pathspec. This is equivalent to setting > the `GIT_ICASE_PATHSPECS` environment variable to `1`. > > +--no-optional-locks:: > + Do not perform optional operations that require locks. This is > + equivalent to setting the `GIT_OPTIONAL_LOCKS` to `0`. > + > GIT COMMANDS > ------------ > > @@ -697,6 +701,15 @@ of clones and fetches. > which feed potentially-untrusted URLS to git commands. See > linkgit:git-config[1] for more details. > > +`GIT_OPTIONAL_LOCKS`:: > + If set to `0`, Git will avoid performing any operations which > + require taking a lock and which are not required to complete the > + requested operation. For example, this will prevent `git status` > + from refreshing the index as a side effect. This is useful for > + processes running in the background which do not want to cause > + lock contention with other operations on the repository. > + Defaults to `1`.
I don't think we should pass this environment variable to remote repositories. It should be listed in local_repo_env[] in environment.c.
-- Hannes