Re: [PATCH v2 07/12] git remote doc: correct dangerous lies about what prune does

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 22, 2018, 20:01 UTC
Message-ID: <xmqq7es9mzna.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <20180121000304.32323-8-avarab@gmail.com>

Ævar Arnfjörð Bjarmason  <avarab@gmail.com> writes:

> +Deletes stale references associated with <name>. By default stale
> +remote-tracking branches under <name>, but depending on global
> +configuration and the configuration of the remote we might even prune
> +local tags....

An optional clarification

    s/prune local tags/& that haven't been pushed there/

> +... Equivalent to `git fetch <name> --prune`, except that no
> +new references will be fetched.

`git fetch --prune <name>` (dashed options first and then non options), just like you wrote in the previous step.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.