Output is too verbose with multiple branches about grunt-compare-size

[rwaldron]

Y U NO use grunt compare_size_empty?

[dmethvin]

Well, regardless of the method used for emptying the list, the root problem is that the current setup works well for light contributors with one or two branches but not so well for repo collabs who deal with a dozen or more. At least for my workflow I only care about size vs. master.

[rwaldron]

cc @gibson042

[gibson042]

I'd like to address this with something like compare_size_prune:<entry to keep>:<entry to keep>:…, basically creating an alias for empty (or replacing it outright) and accepting optional arguments for which entries to keep.