Re: [PATCH] fetch: document that pruning happens before fetching
- From
Jacob Keller <jacob.keller@gmail.com>
- Date
- Jun 14, 2016, 06:14 UTC
- Message-ID
- <CA+P7+xpk6HqeJfUcAkpTbW_hO6dyjanXoqaaKqdTU363n=-Stw@mail.gmail.com>
- In-Reply-To
- <20160613235850.GA8009@sigill.intra.peff.net>
On Mon, Jun 13, 2016 at 4:58 PM, Jeff King <peff@peff.net> wrote:
Show 25 quoted lines
> This was changed in 10a6cc8 (fetch --prune: Run prune before > fetching, 2014-01-02), but it seems that nobody in that > discussion realized we were advertising the "after" > explicitly. > > Signed-off-by: Jeff King <peff@peff.net> > --- > I include myself in that "nobody" of course. :) > > Documentation/fetch-options.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt > index 036edfb..b05a834 100644 > --- a/Documentation/fetch-options.txt > +++ b/Documentation/fetch-options.txt > @@ -52,7 +52,7 @@ ifndef::git-pull[] > > -p:: > --prune:: > - After fetching, remove any remote-tracking references that no > + Before fetching, remove any remote-tracking references that no > longer exist on the remote. Tags are not subject to pruning > if they are fetched only because of the default tag > auto-following or due to a --tags option. However, if tags
What's the difference in behavior due to pruning before instead of after? Curious. It seems like pruning after would make more sense?