From: Phillip Wood <phillip.wood123@gmail.com>
To: Justin Tobler <jltobler@gmail.com>, git@vger.kernel.org
Cc: ps@pks.im, alan@norbauer.com
Subject: Re: [PATCH v3 0/3] clone: suppress unexpected advice message during clone
Date: Tue, 25 Mar 2025 14:35:40 +0000 [thread overview]
Message-ID: <69ccc682-3f81-440f-8e96-a5af5d49fa60@gmail.com> (raw)
In-Reply-To: <20250325005148.1771502-1-jltobler@gmail.com>
Hi Justin
The range-diff below looks good to me, Thanks for working on this
Phillip
On 25/03/2025 00:51, Justin Tobler wrote:
> Range-diff against v2:
> 1: 4dae06d2dd = 1: 4dae06d2dd remote: allow `guess_remote_head()` to suppress advice
> 2: 1180caabf1 ! 2: 2a69b881c4 builtin/clone: suppress unexpected default branch advice
> @@ Commit message
> Signed-off-by: Justin Tobler <jltobler@gmail.com>
>
> ## builtin/clone.c ##
> +@@ builtin/clone.c: static struct ref *wanted_peer_refs(struct clone_opts *opts,
> + if (head)
> + tail_link_ref(head, &tail);
> + if (option_single_branch)
> +- refs = to_free = guess_remote_head(head, refs, 0);
> ++ refs = to_free =
> ++ guess_remote_head(head, refs,
> ++ REMOTE_GUESS_HEAD_QUIET);
> + } else if (option_single_branch) {
> + local_refs = NULL;
> + tail = &local_refs;
> @@ builtin/clone.c: int cmd_clone(int argc,
> }
>
> @@ t/t5607-clone-bundle.sh: test_expect_success 'git bundle v3 rejects unknown capa
> + git -C bundle-repo commit --allow-empty -m init &&
> + git -C bundle-repo bundle create repo.bundle --all &&
> + GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME= \
> -+ git clone bundle-repo/repo.bundle clone-repo 2>err &&
> ++ git clone --single-branch bundle-repo/repo.bundle clone-repo 2>err &&
> +
> + test_grep ! "hint: " err
> +'
> 3: 6fef1d070c = 3: 98b32cdc99 advice: allow disabling default branch name advice
>
> base-commit: 683c54c999c301c2cd6f715c411407c413b1d84e
next prev parent reply other threads:[~2025-03-25 14:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 9:53 bug: git shows hints that should be suppressed alan
2025-03-19 9:58 ` alan
2025-03-19 14:45 ` Elijah Newren
2025-03-20 1:36 ` Justin Tobler
2025-03-20 1:46 ` [PATCH 0/2] clone: suppress unexpected advice message during clone Justin Tobler
2025-03-20 1:46 ` [PATCH 1/2] remote: allow `guess_remote_head()` to suppress advice Justin Tobler
2025-03-20 5:13 ` Patrick Steinhardt
2025-03-20 23:30 ` Justin Tobler
2025-03-21 8:52 ` Junio C Hamano
2025-03-20 1:46 ` [PATCH 2/2] clone: suppress unexpected default branch advice Justin Tobler
2025-03-20 5:13 ` Patrick Steinhardt
2025-03-20 23:36 ` Justin Tobler
2025-03-20 11:10 ` [PATCH 0/2] clone: suppress unexpected advice message during clone Phillip Wood
2025-03-20 23:48 ` Justin Tobler
2025-03-21 16:42 ` Phillip Wood
2025-03-21 23:16 ` [PATCH v2 0/3] " Justin Tobler
2025-03-21 23:16 ` [PATCH v2 1/3] remote: allow `guess_remote_head()` to suppress advice Justin Tobler
2025-03-24 9:31 ` Phillip Wood
2025-03-24 15:21 ` Justin Tobler
2025-03-24 19:29 ` phillip.wood123
2025-03-21 23:16 ` [PATCH v2 2/3] builtin/clone: suppress unexpected default branch advice Justin Tobler
2025-03-24 9:32 ` Phillip Wood
2025-03-24 15:35 ` Justin Tobler
2025-03-21 23:16 ` [PATCH v2 3/3] advice: allow disabling default branch name advice Justin Tobler
2025-03-24 9:32 ` Phillip Wood
2025-03-23 19:38 ` [PATCH v2 0/3] clone: suppress unexpected advice message during clone Junio C Hamano
2025-03-25 0:51 ` [PATCH v3 " Justin Tobler
2025-03-25 0:51 ` [PATCH v3 1/3] remote: allow `guess_remote_head()` to suppress advice Justin Tobler
2025-03-25 0:51 ` [PATCH v3 2/3] builtin/clone: suppress unexpected default branch advice Justin Tobler
2025-03-25 0:51 ` [PATCH v3 3/3] advice: allow disabling default branch name advice Justin Tobler
2025-03-25 14:35 ` Phillip Wood [this message]
2025-03-20 4:05 ` bug: git shows hints that should be suppressed alan
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=69ccc682-3f81-440f-8e96-a5af5d49fa60@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=alan@norbauer.com \
--cc=git@vger.kernel.org \
--cc=jltobler@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=ps@pks.im \
/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).