Junio C Hamano wrote: > Jakub Narebski <jnareb@xxxxxxxxx> writes: > >> Shawn Pearce wrote: >> >>> Andy Parkins <andyparkins@xxxxxxxxx> wrote: >>>> * git-show-branch output is cryptic. >>> >>> Agreed. I still don't know how to read its output. So I just >>> don't use it. Ever. :-) >> >> And the way it uses it's options is even more cryptic, and differs from >> other similar commands. > > (Jakub, please do not drop people from cc: list; you were asked > more than once). The problem is that I'm not subscribed to git mailing list; I usually read it via GMane news<->mail interface, at nntp://news.gmane.org/gmane.comp.version-control.git First, in this interface I have only the last author and not the full Cc: list. Second, when I reply _both_ via email (adding authors if necessary) and to news, people receiving my reply don't have (I guess) git@xxxxxxxxxxxxxxx in Cc: list, so sometimes the discussion drops off the list. Third, if I add git mailing list address when replying via mail, vger server blocks email from gmane stating Technical details of permanent failure: PERM_FAILURE: SMTP Error (state 9): 501 5.1.3 Path data: Had characters unsuitable for an rfc821-string When email is sent _directly_ to me (i.e. I'm on Cc: list) I try to preserve Cc: list. > Ok, so what's the action you guys are proposing? > > (1) show-branch input is cryptic and it does not do anything > useful. Drop it. > > (2) show-branch input is cryptic and I do not understand what > it is trying to do. Document it better. [...] I'm just used to the way revisions are specified to other history viewers: git-log (via git-rev-list), gitk, qgit. git-show-branch is a bit odd man out here. "git-show-branch ref1 ref2 ref3" is (without --more=n) like git rev-list ref1 ref2 ref3 --not $(git merge-base ref1 ref2 ref3) Which is handy for git-show-branch, but odd. Perhaps we should add --xor option to git rev list for the above, i.e. git rev-list A...B == == git rev-list A B --not $(git merge-base A B) git rev-list --xor A B C == == git rev-list A B C --not $(git merge-base A B C) > Personally, I find its input branch globbing very handy, and > often wish that 'git branch' had a '--list' option that lists > branches that match the glob pattern given on the command line, > not just listing everything when no parameter is given. It is odd (git branch not having --list with globbing) also because 'git tag' has globbing support. -- Jakub Narebski Poland - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html