Hi, On Sun, 9 Nov 2008, Alex Riesen wrote: > Linus Torvalds, Fri, Nov 07, 2008 19:08:36 +0100: > > On Fri, 7 Nov 2008, Alex Riesen wrote: > > > > > > Does not work if there are ranges given :-/ > > > It'd be very nice to have: git show #c1..$c2 $c3 $c4 $c5..$c6 > > > > Yeah, we've very fundamentally never supported that. Not for show, but > > also not for anything else (ie "gitk a..b c..d" does _not_ give you > > two ranges). > > > > It's easy to see why once you understand what 'a..b' really means (ie > > it just expands to '^a' and 'b'), and how it's not really a "range" > > operation as much as a set operation that interacts with all the other > > arguments too. But unless you're very aware of that, it can be > > surprising. > > > > Oh, I am. But it is just so convenient to have range support for > commands which just show commits. Besides, git-show just errors out, > instead of producing the commits like git-log does. Have fun implementing the support, and then explaining to users why this shows only one commit: git show HEAD^..HEAD HEAD~10 Ciao, Dscho -- 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
