Duy Nguyen venit, vidit, dixit 16.05.2013 10:23: > On Thu, May 16, 2013 at 3:00 PM, Michael J Gruber > <g...@drmicha.warpmail.net> wrote: >> I feel, though, that we're really exploding our option and config realm. >> For "git branch" in list mode, we are already able to stack "-v", i.e. >> "-v" and "-vv" do different things. How about maybe adding "-vvv" and >> arranging things so that the verbosity and the run time increases with >> the number of v's? >> >> -v list with sha1 + subject of last commit >> -vv add upstream branch name >> -vvv add ahead/behind info (the only costly mode) >> -vvvv same with "--cherry" (ahead/behind/same) >> >> Or maybe combine the middle two cases into "-vv", which means it would >> be the same as "-vv", with only "-v" changing what it does now. > > What if I want something in -vvvv except some in -vv? I think to avoid > option explosion, maybe we can adopt --pretty=format:xxx from "git > log" and let the user decideswhat (and how) to display. "pretty" code > learns about alignment already, which may be useful here. > -- > Duy
Sure, that is the big solution we've been talking about. Unify for-each-ref formats and log formats and use that. After all, "git branch" in list mode really is for-each-ref, and should be transparently so; same goes for "git tag". Think "git rev-list" and "git ref-list"! But I guess we'll be compabeaten ;) Michael -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
