Re: [BUG] git remote prune removes local tags, depending on fetch config
- From
Kevin Daudt <me@ikke.info>
- Date
- Jan 18, 2018, 06:18 UTC
- Message-ID
- <20180118061814.GC5618@alpha.vpn.ikke.info>
- In-Reply-To
- <874lnmkorz.fsf@linux-m68k.org>
On Tue, Jan 16, 2018 at 12:48:32PM +0100, Andreas Schwab wrote:
Show 12 quoted lines
> On Jan 15 2018, Michael Giuffrida <michaelpg@chromium.org> wrote: > > > It doesn't seem like a useful feature -- you wouldn't expect `git > > fetch --prune` to remove your local branches that you were developing > > on, right? > > Don't mix local and remote refs. There is a reason why remote tracking > branches are put in a separate name space. If you fetch the remote tags > into a separate name space (eg. refs/remote/tags/*:refs/tags/*) then > there is no conflict. > > Andreas.
But then they are no longer considered tags, but remote tracking branches. Tools like git tag and git describe won't consider them, and git branch -r would show them as remote tracking branches.
Show 5 quoted lines
> > -- > Andreas Schwab, schwab@linux-m68k.org > GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 > "And now for something completely different."