Re: [PATCH 6/9] Documentation: branch: update --merged description
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:47:30
Jonathan Nieder [off-list ref] writes:
Update the documentation for --merged and --no-merged to explain the meaning of the optional parameter introduced in commit 049716b (branch --merged/--no-merged: allow specifying arbitrary commit, 2008-07-08). Signed-off-by: Jonathan Nieder <redacted>
Thanks. I most often use --no-merged this way: $ git branch --no-merged pu to see topics that are queued but not merged anywhere. This is not about "do not list", but "do show the ones that are not merged", so I reworded the description of the latter in your patch.
quoted hunk ↗ jump to hunk
diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt index aad71dc..e8b32a2 100644 --- a/Documentation/git-branch.txt +++ b/Documentation/git-branch.txt@@ -134,11 +134,13 @@ start-point is either a local or remote branch. --contains <commit>:: Only list branches which contain the specified commit. ---merged:: - Only list branches which are fully contained by HEAD. +--merged [<commit>]:: + Only list branches whose tips are reachable from the + specified commit (HEAD if not specified). ---no-merged:: - Do not list branches which are fully contained by HEAD. +--no-merged [<commit>]:: + Only list branches whose tips are not reachable from the + specified commit (HEAD if not specified). <branchname>:: The name of the branch to create or delete.-- 1.6.5.rc1.199.g596ec -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html