From: Johannes Sixt <j6t@kdbg.org>
To: Jeff King <peff@peff.net>
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] git: add --no-optional-locks option
Date: Thu, 21 Sep 2017 20:25:50 +0200 [thread overview]
Message-ID: <7a2d895c-df8c-1305-234f-7f8e2b271ec2@kdbg.org> (raw)
In-Reply-To: <20170921043214.pyhdsrpy4omy54rm@sigill.intra.peff.net>
Am 21.09.2017 um 06:32 schrieb Jeff King:
> 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
next prev parent reply other threads:[~2017-09-21 18:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 4:32 [PATCH] git: add --no-optional-locks option Jeff King
2017-09-21 4:55 ` Junio C Hamano
2017-09-21 5:08 ` Jeff King
2017-09-21 5:29 ` Junio C Hamano
2017-09-21 18:25 ` Johannes Sixt [this message]
2017-09-22 4:25 ` Jeff King
2017-09-22 11:22 ` Jeff Hostetler
2017-09-22 15:04 ` Jeff King
2017-09-22 20:09 ` Stefan Beller
2017-09-22 21:25 ` Jeff King
2017-09-22 21:41 ` Stefan Beller
2017-09-23 3:34 ` Jeff King
2017-09-25 18:51 ` Stefan Beller
2017-09-27 6:44 ` Jeff King
2017-09-22 6:42 ` Daniel Santos
2017-09-22 16:04 ` Jeff King
2017-09-24 11:31 ` Kaartic Sivaraam
2017-09-25 16:17 ` Johannes Schindelin
2017-09-26 14:44 ` Jeff Hostetler
2017-09-25 16:10 ` Johannes Schindelin
2017-09-25 17:00 ` Jeff King
[not found] ` <79ed4c34-1727-7c1e-868a-1206902638ad@gmail.com>
2017-09-27 6:40 ` Jeff King
2017-09-27 13:50 ` Kaartic Sivaraam
2017-09-27 16:28 ` Jeff King
2017-09-27 6:54 ` [PATCH v2] " Jeff King
2017-09-28 16:15 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7a2d895c-df8c-1305-234f-7f8e2b271ec2@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).