Re: [PATCH 2/2] Teach 'git remote' how to cleanup stale tracking branches.
From: Jakub Narebski <hidden>
Date: 2016-06-15 22:42:52
Possibly related (same subject, not in this thread)
- 2016-06-15 · Re: [PATCH 2/2] Teach 'git remote' how to cleanup stale tracking branches. · Junio C Hamano <hidden>
- 2016-06-15 · Re: [PATCH 2/2] Teach 'git remote' how to cleanup stale tracking branches. · Shawn O. Pearce <hidden>
Shawn O. Pearce wrote:
quoted hunk ↗ jump to hunk
diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt index 358c1ac..817651e 100644 --- a/Documentation/git-remote.txt +++ b/Documentation/git-remote.txt@@ -12,6 +12,7 @@ SYNOPSIS 'git-remote' 'git-remote' add <name> <url> 'git-remote' show <name> +'git-remote' prune <name> DESCRIPTION -----------@@ -26,6 +27,10 @@ update remote-tracking branches <name>/<branch>. In the third form, gives some information about the remote <name>. +In the fourth form, deletes all stale tracking branches under <name>. +These stale branches have already been removed from the remote repository +referenced by <name>, but are still locally available in "remotes/<name>". +
Wouldn't it be better to refer to subcommand by name, instead of
the number of subcommand ("fourth form")? Compare git-rerere(1).
P.S. I wanted to refer to documentation of other commands with
subcommands, but git-bisect(1) is not good example; git-rerere(1)
I think is.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git