Re: [PATCH 11/15] fetch --prune: prune only based on explicit refspecs

Michael Haggerty mhag...@alum.mit.edu writes: On 10/24/2013 11:11 PM, Junio C Hamano wrote: ... We should just lose It is similar to using from 10/15 and start over, perhaps? Add the first paragraph of the below in 10/15 and add the rest in 11/15, or something. --tags::

Re: [PATCH 11/15] fetch --prune: prune only based on explicit refspecs

On 10/24/2013 11:11 PM, Junio C Hamano wrote: Michael Haggerty mhag...@alum.mit.edu writes: ... Signed-off-by: Michael Haggerty mhag...@alum.mit.edu Everything in the proposed log message made sense to me. diff --git a/Documentation/config.txt b/Documentation/config.txt index

Re: [PATCH 11/15] fetch --prune: prune only based on explicit refspecs

Michael Haggerty mhag...@alum.mit.edu writes: ... Signed-off-by: Michael Haggerty mhag...@alum.mit.edu Everything in the proposed log message made sense to me. diff --git a/Documentation/config.txt b/Documentation/config.txt index d4d93c9..83c1700 100644 --- a/Documentation/config.txt +++

[PATCH 11/15] fetch --prune: prune only based on explicit refspecs

The old behavior of fetch --prune was to prune whatever was being fetched. In particular, fetch --prune --tags caused tags not only to be fetched, but also to be pruned. This is inappropriate because there is only one tags namespace that is shared among the local repository and all remotes.