Re: [BUG] git remote prune removes local tags, depending on fetch config

On Tue, Jan 16, 2018 at 12:48:32PM +0100, Andreas Schwab wrote: > On Jan 15 2018, Michael Giuffrida 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? > >

Re: [BUG] git remote prune removes local tags, depending on fetch config

On Jan 15 2018, Michael Giuffrida 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

Re: [BUG] git remote prune removes local tags, depending on fetch config

On Tue, Jan 16 2018, Michael Giuffrida jotted: > Just to confirm, you're talking about the behavior of removing *all* > tags that aren't found on the remote? (Not just tags that used to be > on some remote, but have since been removed from that remote.) So, > with your proposed workflow, you

Re: [BUG] git remote prune removes local tags, depending on fetch config

Just to confirm, you're talking about the behavior of removing *all* tags that aren't found on the remote? (Not just tags that used to be on some remote, but have since been removed from that remote.) So, with your proposed workflow, you would never create your own tags locally, without pushing

Re: [BUG] git remote prune removes local tags, depending on fetch config

On Mon, Jan 15 2018, Michael Giuffrida jotted: > `git remote prune ` should "delete all stale remote-tracking > branches under ". I was surprised to discover, after some > troubleshooting, that it also deletes *all* local tags that don't > exist on the remote, if the following refspec is

[BUG] git remote prune removes local tags, depending on fetch config

`git remote prune ` should "delete all stale remote-tracking branches under ". I was surprised to discover, after some troubleshooting, that it also deletes *all* local tags that don't exist on the remote, if the following refspec is included in the remote's fetch config: