From: Junio C Hamano <gitster@pobox.com>
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 14:29:30 +0900 [thread overview]
Message-ID: <xmqq377gliv9.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170921050835.mrbgx2zryy3jusdk@sigill.intra.peff.net> (Jeff King's message of "Thu, 21 Sep 2017 01:08:36 -0400")
Jeff King <peff@peff.net> writes:
> I admit that's just adding more hand-waving to the pile. But I don't
> think it really _hurts_ to leave that door open (aside from making the
> documentation a bit wishy-washy). And it helps because callers would
> pick up the new features automatically, without having to learn about a
> new option.
Oh, I do agree it is a good idea to leave that door open, so that
scripts that rely on today's --no-optional-locks option will not
have to be updated when a similar feature (like the "ref compaction"
example you mentioned) against which "let's disable when we are not
the primary process, in order to keep the interference to the
minimum" would be something we would want to say. The option being
added here should cover these future needs.
> And I think that's really what this option is. It is less about the
> caller asking for some specific behavior, and more about them telling
> Git about the context in which it's executing so it can make intelligent
> decisions.
Yes, indeed.
next prev parent reply other threads:[~2017-09-21 5:29 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 [this message]
2017-09-21 18:25 ` Johannes Sixt
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=xmqq377gliv9.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--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).