Hi, On Mon, 10 Nov 2008, Alex Riesen wrote: > 2008/11/10 Johannes Schindelin <Johannes.Schindelin@xxxxxx>: > > On Sun, 9 Nov 2008, Alex Riesen wrote: > >> > >> 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 > > > > for cs in HEAD^..HEAD HEAD~10; do > case "$cs"; in > *..*) > git format-patch --stdout "$cs" > ;; > *) > git show --pretty=email "$cs" > ;; > esac > done > > At least, this is what I have in mind and how I expect it to work. That is not the way git-show is implemented (it uses setup_revisions() to check for validity and to parse the arguments), and I cannot think of any way to make this work without ugly workarounds. 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
