From: "Ben Denhartog" <ben@sudoforge.com>
To: git@vger.kernel.org
Subject: --no-tags doesn't appear to be working as intended
Date: Sat, 02 May 2020 14:01:35 -0700 [thread overview]
Message-ID: <7480e635-97cc-4acd-875e-54bc71a88068@www.fastmail.com> (raw)
From the documentation, it would appear that `--no-tags` should avoid pulling tags, even if they point to refs which match the refspec being fetched:
> -n, --no-tags
> By default, tags that point at objects that are downloaded from the remote repository are fetched and
> stored locally. This option disables this automatic tag following. The default behavior for a remote may
> be specified with the remote.<name>.tagOpt setting. See git-config(1).
This, however, does not appear to be the case: Either using the `--no-tags` flag on the command line directly or setting `remote.<name>.tagopt = --no-tags` appears to be ignored when running `git-fetch`. This can be recreated simply:
```
# /tmp/a will be our "origin"
# /tmp/b will be our "fork"
mkdir /tmp/{a,b}
# set up the origin
git -C /tmp/a init
echo "Hello, world" >/tmp/a/README
git -C /tmp/a add README
git -C /tmp/a commit -m 'initial commit'
git -C /tmp/a tag 0.0.1 HEAD
# set up the fork
git -C /tmp/b init
git -C /tmp/b remote add -f --no-tags upstream file:///tmp/a
```
You'll see the 0.0.1 tag being fetched. You can delete it all you want, set the `remote.upstream.tagopt = --no-tags`, etc -- it will always be pulled. This is the opposite behavior I would expect based on the available documentation and discussion around the tag in the mailing list.
--
Ben Denhartog
ben@sudoforge.com
next reply other threads:[~2020-05-02 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 21:01 Ben Denhartog [this message]
2020-05-03 6:54 ` --no-tags doesn't appear to be working as intended Jeff King
2020-05-03 18:27 ` Ben Denhartog
-- strict thread matches above, loose matches on Subject: below --
2020-05-02 22:20 Ben Denhartog
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=7480e635-97cc-4acd-875e-54bc71a88068@www.fastmail.com \
--to=ben@sudoforge.com \
--cc=git@vger.kernel.org \
/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).