Re: [q] git-diff --reverse 7def2be1..7def2be1^
- From
- Ingo Molnar <mingo@elte.hu>
- Date
- Jun 20, 2008, 10:00 UTC
- Message-ID
- <20080620100038.GB10704@elte.hu>
- In-Reply-To
- <7v3an8o5mm.fsf@gitster.siamese.dyndns.org>
* Junio C Hamano <gitster@pobox.com> wrote:
Show 14 quoted lines
> By the way, not linking --reverse (traverse the history normally and > then show the commits in the reverse order than usual) to -R (show > diff in the opposite way while showing the change each commit > introduces) allows you to even say "log --reverse -R", which did not > come from a conscious design, but being able to say this _is_ a > conscious design: > > $ git fetch j6t > $ git log --reverse -p ..j6t/for-junio > > When I review a branch somebody else offers me, I may want to view the > commits on them in reverse order (so that they build a bit by bit on > top of my tree), but I _certainly_ do not want to view the patch in > reverse!
yes, i too do that occasionally (and some of my export/import scripts rely on it in fact), and i was not suggesting to change any existing functionality anyway.
Ingo