From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: git@vger.kernel.org, "Eric Sunshine" <sunshine@sunshineco.com>,
"Elijah Newren" <newren@gmail.com>,
"Jean-Noël AVILA" <jn.avila@free.fr>
Subject: Re: ds/sparse-checkout-requires-per-worktree-config (was Re: What's cooking in git.git (Feb 2022, #02; Wed, 9))
Date: Fri, 11 Feb 2022 08:51:23 -0800 [thread overview]
Message-ID: <xmqqfsope48k.fsf@gitster.g> (raw)
In-Reply-To: <f36712f5-28bd-42d7-3ea1-f4afa328be07@gmail.com> (Derrick Stolee's message of "Fri, 11 Feb 2022 08:40:05 -0500")
Derrick Stolee <stolee@gmail.com> writes:
> On 2/9/2022 7:12 PM, Junio C Hamano wrote:
>
>> * ds/sparse-checkout-requires-per-worktree-config (2022-02-08) 6 commits
>> ...
>> Will merge to 'next'?
>> cf. <20220204081336.3194538-1-newren@gmail.com>
>> cf. <CAPig+cRrRxuTeByhKkLs_KDaWY8-r4+jrwT83A-r+sBQsmebMw@mail.gmail.com>
>> source: <pull.1101.v6.git.1644269583.gitgitgadget@gmail.com>
>
> You and I have had a good discussion about the latest version. I
> think we've mostly landed on finding ways to improve documentation
> in other ways (including the patch you submitted), but here are
> the things that I see as still outstanding:
Thanks for a clearly written summary. Very much appreciated.
With the maintainer hat on, I agree that all are good points. From
a reviewer's point of view, I do not care too deeply about 1 or 2
myself though.
> 0. Eric mentioned earlier that he was interested in looking again,
> but has not signaled that his review is complete.
>
> 1. You and Eric disagree about the use of "worktree" and "working
> tree" in the documentation. I could revert the change to these
> docs from v5 to v6.
>
> 2. You mention that the changes in config.c could be split into
> two (first, create repo_config_set_multivar_gently() and then
> create repo_config_set_worktree_gently()).
>
> 3. Jean-Noël noticed an improvement to reduce work on translators.
> The diff below could be squashed into patch 5 OR I could submit
> it as a forward fix.
>
> diff --git a/builtin/worktree.c b/builtin/worktree.c
> index c6eb636329a..7c272078dc9 100644
> --- a/builtin/worktree.c
> +++ b/builtin/worktree.c
> @@ -384,11 +384,13 @@ static int add_worktree(const char *path, const char *refname,
> bare &&
> git_config_set_multivar_in_file_gently(
> to_file, "core.bare", NULL, "true", 0))
> - error(_("failed to unset 'core.bare' in '%s'"), to_file);
> + error(_("failed to unset '%s' in '%s'"),
> + "core.bare", to_file);
> if (!git_configset_get_value(&cs, "core.worktree", &core_worktree) &&
> git_config_set_in_file_gently(to_file,
> "core.worktree", NULL))
> - error(_("failed to unset 'core.worktree' in '%s'"), to_file);
> + error(_("failed to unset '%s' in '%s'"),
> + "core.worktree", to_file);
>
> git_configset_clear(&cs);
> }
>
> Thanks,
> -Stolee
next prev parent reply other threads:[~2022-02-11 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 0:12 What's cooking in git.git (Feb 2022, #02; Wed, 9) Junio C Hamano
2022-02-11 13:40 ` ds/sparse-checkout-requires-per-worktree-config (was Re: What's cooking in git.git (Feb 2022, #02; Wed, 9)) Derrick Stolee
2022-02-11 16:51 ` Junio C Hamano [this message]
2022-02-15 22:40 ` Eric Sunshine
2022-02-16 1:55 ` Junio C Hamano
2022-02-11 21:01 ` What's cooking in git.git (Feb 2022, #02; Wed, 9) Jean-Noël AVILA
2022-02-11 22:38 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqfsope48k.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
--cc=newren@gmail.com \
--cc=stolee@gmail.com \
--cc=sunshine@sunshineco.com \
/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.
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 NNTP newsgroup(s).