From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_PASS, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id A2EB61F8C1 for ; Sun, 3 May 2020 06:54:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727107AbgECGyt (ORCPT ); Sun, 3 May 2020 02:54:49 -0400 Received: from cloud.peff.net ([104.130.231.41]:34952 "HELO cloud.peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1727026AbgECGys (ORCPT ); Sun, 3 May 2020 02:54:48 -0400 Received: (qmail 19360 invoked by uid 109); 3 May 2020 06:54:48 -0000 Received: from Unknown (HELO peff.net) (10.0.1.2) by cloud.peff.net (qpsmtpd/0.94) with SMTP; Sun, 03 May 2020 06:54:48 +0000 Authentication-Results: cloud.peff.net; auth=none Received: (qmail 4392 invoked by uid 111); 3 May 2020 06:54:48 -0000 Received: from coredump.intra.peff.net (HELO sigill.intra.peff.net) (10.0.0.2) by peff.net (qpsmtpd/0.94) with (TLS_AES_256_GCM_SHA384 encrypted) ESMTPS; Sun, 03 May 2020 02:54:48 -0400 Authentication-Results: peff.net; auth=none Date: Sun, 3 May 2020 02:54:46 -0400 From: Jeff King To: Ben Denhartog Cc: git@vger.kernel.org Subject: Re: --no-tags doesn't appear to be working as intended Message-ID: <20200503065446.GA1829906@coredump.intra.peff.net> References: <7480e635-97cc-4acd-875e-54bc71a88068@www.fastmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <7480e635-97cc-4acd-875e-54bc71a88068@www.fastmail.com> Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Sat, May 02, 2020 at 02:01:35PM -0700, Ben Denhartog wrote: > # 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. I don't see that behavior. I get: $ git -C /tmp/b remote add -f --no-tags upstream file:///tmp/a Updating upstream remote: Enumerating objects: 3, done. remote: Counting objects: 100% (3/3), done. remote: Total 3 (delta 0), reused 0 (delta 0), pack-reused 0 Unpacking objects: 100% (3/3), 197 bytes | 197.00 KiB/s, done. From file:///tmp/a * [new branch] master -> upstream/master Is it possible you have some other config that might be conflicting (e.g., extra refspecs that ask to transfer tags)? What does "git config --list --show-origin" say? -Peff