git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Toon Claes <toon@iotcl.com>
Cc: git@vger.kernel.org,
	"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>,
	"Michal Suchánek" <msuchanek@suse.de>,
	"Jeff King" <peff@peff.net>
Subject: Re: [PATCH v4 4/6] clone: add tags refspec earlier to fetch refspec
Date: Mon, 3 Feb 2025 08:51:27 +0100	[thread overview]
Message-ID: <Z6B1f1jB8KoTp8P8@pks.im> (raw)
In-Reply-To: <20250131-toon-clone-refs-v4-4-2a4ff851498f@iotcl.com>

On Fri, Jan 31, 2025 at 04:30:32PM +0100, Toon Claes wrote:
> In clone.c we call refspec_ref_prefixes() to copy the fetch refspecs
> from the `remote->fetch` refspec into `ref_prefixes` of
> `transport_ls_refs_options`. Afterward we add the tags prefix

s/Afterward/&s/

> diff --git a/builtin/clone.c b/builtin/clone.c
> index d652682494d0d27dd73cd0585e28b23f2883786d..7ab156ac00240de89baca6533ed2541839286fc4 100644
> --- a/builtin/clone.c
> +++ b/builtin/clone.c
> @@ -1375,14 +1365,15 @@ int cmd_clone(int argc,
>  		transport->smart_options->check_self_contained_and_connected = 1;
>  
>  	strvec_push(&transport_ls_refs_options.ref_prefixes, "HEAD");
> +
> +	if (option_tags || option_branch)
> +		refspec_append(&remote->fetch, TAG_REFSPEC);

It's a bit surprising that we also do this with `option_branch`, which
only seems to indicate which branch git-clone(1) is supposed to check
out. But in fact, the documentation mentions that it may also be used to
check out a tag. Principle of least surprise at its best.

In any case, I think it would be nice to have a comment here explaining
why this is the correct thing to do.

Patrick

  reply	other threads:[~2025-02-03  7:51 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29 12:00 [PATCH v2] builtin/clone: teach git-clone(1) the --revision= option Toon Claes
2024-12-02 14:08 ` Patrick Steinhardt
2024-12-02 21:17   ` Jeff King
2024-12-03 15:34   ` Michal Suchánek
2024-12-19 11:23   ` Toon Claes
2024-12-19 11:58 ` [PATCH v3] " Toon Claes
2024-12-19 18:30   ` Junio C Hamano
2025-01-31 15:30   ` [PATCH v4 0/6] Enable doing a shallow clone of a specific git revision Toon Claes
2025-01-31 15:30     ` [PATCH v4 1/6] clone: cut down on global variables in clone.c Toon Claes
2025-01-31 15:30     ` [PATCH v4 2/6] clone: make it possible to specify --tags Toon Claes
2025-02-01 16:47       ` Jean-Noël AVILA
2025-01-31 15:30     ` [PATCH v4 3/6] clone: refactor wanted_peer_refs() Toon Claes
2025-02-03  7:51       ` Patrick Steinhardt
2025-01-31 15:30     ` [PATCH v4 4/6] clone: add tags refspec earlier to fetch refspec Toon Claes
2025-02-03  7:51       ` Patrick Steinhardt [this message]
2025-01-31 15:30     ` [PATCH v4 5/6] clone: introduce struct clone_opts in builtin/clone.c Toon Claes
2025-02-03  7:51       ` Patrick Steinhardt
2025-01-31 15:30     ` [PATCH v4 6/6] builtin/clone: teach git-clone(1) the --revision= option Toon Claes
2025-01-31 21:05       ` Junio C Hamano
2025-02-01 16:50       ` Jean-Noël AVILA
2025-02-03  7:51       ` Patrick Steinhardt
2025-02-04 21:33     ` [PATCH v5 0/7] Enable doing a shallow clone of a specific git revision Toon Claes
2025-02-04 21:34       ` [PATCH v5 1/7] clone: cut down on global variables in clone.c Toon Claes
2025-02-04 21:34       ` [PATCH v5 2/7] clone: make it possible to specify --tags Toon Claes
2025-02-05  8:03         ` Patrick Steinhardt
2025-02-05 16:29           ` Toon Claes
2025-02-05 21:15           ` Jean-Noël AVILA
2025-02-04 21:34       ` [PATCH v5 3/7] clone: refactor wanted_peer_refs() Toon Claes
2025-02-04 21:34       ` [PATCH v5 4/7] clone: add tags refspec earlier to fetch refspec Toon Claes
2025-02-05  8:03         ` Patrick Steinhardt
2025-02-04 21:34       ` [PATCH v5 5/7] clone: introduce struct clone_opts in builtin/clone.c Toon Claes
2025-02-04 21:34       ` [PATCH v5 6/7] parse-options: introduce die_for_incompatible_opt2() Toon Claes
2025-02-05  8:03         ` Patrick Steinhardt
2025-02-04 21:34       ` [PATCH v5 7/7] builtin/clone: teach git-clone(1) the --revision= option Toon Claes
2025-02-05  8:03         ` Patrick Steinhardt
2025-02-05 16:43           ` Toon Claes
2025-02-05  8:03       ` [PATCH v5 0/7] Enable doing a shallow clone of a specific git revision Patrick Steinhardt
2025-02-05 14:09       ` Junio C Hamano
2025-02-05 16:47       ` [PATCH v6 " Toon Claes
2025-02-05 16:47         ` [PATCH v6 1/7] clone: cut down on global variables in clone.c Toon Claes
2025-02-05 16:47         ` [PATCH v6 2/7] clone: make it possible to specify --tags Toon Claes
2025-02-05 16:47         ` [PATCH v6 3/7] clone: refactor wanted_peer_refs() Toon Claes
2025-02-05 16:47         ` [PATCH v6 4/7] clone: add tags refspec earlier to fetch refspec Toon Claes
2025-02-05 16:47         ` [PATCH v6 5/7] clone: introduce struct clone_opts in builtin/clone.c Toon Claes
2025-02-05 16:47         ` [PATCH v6 6/7] parse-options: introduce die_for_incompatible_opt2() Toon Claes
2025-02-05 16:47         ` [PATCH v6 7/7] builtin/clone: teach git-clone(1) the --revision= option Toon Claes
2025-02-05 17:24           ` Junio C Hamano
2025-02-06  6:33         ` [PATCH v7 0/7] Enable doing a shallow clone of a specific git revision Toon Claes
2025-02-06  6:33           ` [PATCH v7 1/7] clone: cut down on global variables in clone.c Toon Claes
2025-02-06  6:33           ` [PATCH v7 2/7] clone: make it possible to specify --tags Toon Claes
2025-02-06  6:33           ` [PATCH v7 3/7] clone: refactor wanted_peer_refs() Toon Claes
2025-02-06  6:33           ` [PATCH v7 4/7] clone: add tags refspec earlier to fetch refspec Toon Claes
2025-02-06  6:33           ` [PATCH v7 5/7] clone: introduce struct clone_opts in builtin/clone.c Toon Claes
2025-02-06  6:33           ` [PATCH v7 6/7] parse-options: introduce die_for_incompatible_opt2() Toon Claes
2025-02-06  6:33           ` [PATCH v7 7/7] builtin/clone: teach git-clone(1) the --revision= option Toon Claes
2025-02-06  8:13             ` Patrick Steinhardt
2025-02-06 20:26               ` 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=Z6B1f1jB8KoTp8P8@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=msuchanek@suse.de \
    --cc=peff@peff.net \
    --cc=toon@iotcl.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).