From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, "Brandon Williams" <bmwill@google.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: [PATCH] clone: add a --no-tags option to clone without tags
Date: Tue, 18 Apr 2017 22:32:09 -0700 [thread overview]
Message-ID: <xmqq1ssparom.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: xmqq60i1dvnk.fsf@gitster.mtv.corp.google.com
Junio C Hamano <gitster@pobox.com> writes:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> Add a --no-tags option to "git clone" to clone without tags. Currently
>> there's no easy way to clone a repository and end up with just a
>> "master" branch via --single-branch, or track all branches and no
>> tags. Now --no-tags can be added to "git clone" with or without
>> --single-branch to clone a repository without tags.
>
> Makes sense.
>
>> +--no-tags::
>> + Don't clone any tags, and set `remote.origin.tagOpt=--no-tags`
>> + in the config, ensuring that future `git pull` and `git fetch`
>> + operations won't fetch any tags.
>
> OK. Not just we ignore tags during the initial cloning, we set
> things up so that we do not _follow_ tags in subsequent fetches.
I somewhat doubt the utility of this change. "--single-branch"
already refrains from grabbing all the tags, and the tags it grabs
when "clone" runs and also in subsequent "fetch" are only the ones
relevant to that branch. When a user is fetching say 'maint', it is
very likely that the user wants tags that are reachable from the tip
of 'maint' (if only to make the tip of that branch describable),
even though the user would not care about the tags on the other
branches that are ahead of 'maint'.
It is not that much code, and carrying it is not that much burden,
but I am reasonably sure that I won't use it myself.
next prev parent reply other threads:[~2017-04-19 5:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 21:28 Is there a way to get 'git fetch --no-tags' semantics with 'git clone'? Ævar Arnfjörð Bjarmason
2017-04-18 19:15 ` [PATCH] clone: add a --no-tags option to clone without tags Ævar Arnfjörð Bjarmason
2017-04-18 21:06 ` Ævar Arnfjörð Bjarmason
2017-04-18 23:30 ` Brandon Williams
2017-04-19 1:38 ` Junio C Hamano
2017-04-19 5:32 ` Junio C Hamano [this message]
2017-04-19 14:38 ` [PATCH v2] " Ævar Arnfjörð Bjarmason
2017-04-25 22:45 ` Jonathan Nieder
2017-04-26 1:26 ` Junio C Hamano
2017-04-26 8:56 ` Ævar Arnfjörð Bjarmason
2017-04-25 22:35 ` [PATCH] " Jonathan Nieder
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=xmqq1ssparom.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.