Re: [puzzled and solved] "shortlog" not quite understanding all "log" options

2014-06-18 Thread Jeff King
On Fri, May 30, 2014 at 02:37:02PM -0700, Junio C Hamano wrote: > > I am slightly puzzled why parse_revision_opt does not just call > > handle_revision_pseudo_opt. According to f6aca0dc4, it is because > > pseudo-options need to be acted on in-order, as they affect things like > > subsequent "--no

Re: [puzzled and solved] "shortlog" not quite understanding all "log" options

2014-05-30 Thread Junio C Hamano
Jeff King writes: > On Fri, May 30, 2014 at 12:28:47PM -0700, Junio C Hamano wrote: > >> Aaaand, it turns out that the answer is in the big comment at >> the beginning of handle_revision_pseudo_opt(). >> >> -- >8 -- >> Subject: shortlog: allow --exclude= to be passed >> >> e7b432c5 (revisi

Re: [puzzled and solved] "shortlog" not quite understanding all "log" options

2014-05-30 Thread Jeff King
On Fri, May 30, 2014 at 12:28:47PM -0700, Junio C Hamano wrote: > Aaaand, it turns out that the answer is in the big comment at > the beginning of handle_revision_pseudo_opt(). > > -- >8 -- > Subject: shortlog: allow --exclude= to be passed > > e7b432c5 (revision: introduce --exclude= to ta

[puzzled and solved] "shortlog" not quite understanding all "log" options

2014-05-30 Thread Junio C Hamano
This gives the list of all recent commits but not the ones that are only reachable from the notes hierarchy: $ git log --exclude=refs/notes/\* --all --no-merges --since=18.hours | git shortlog and we are supposed to be able to write the same with shortlog itself, i.e. $ git shortlog --exclude=