On Fri, 30 Jun 2006, Michal Ludvig wrote:
>
> Linus Torvalds wrote:
>
> > git log -p --full-diff v2.6.16.. crypto/
>
> Can I somehow get the result in a reverse order, i.e. oldest commits first?
Not that way, no. "git log" generates the data on-the-fly, so a simple
"git log" will always give most recent first.
However, you can do this
git log --pretty=oneline v2.6.16.. crypto/
to generate a list of commits, one per line. Then, reverse that list
("tac" is your friend), and feed it back to "git-diff-tree --stdin
--pretty -p" to get the diffs.
So
git log --pretty=oneline v2.6.16.. crypto/ |
tac |
git-diff-tree --stdin --pretty -p
should do what you want.
Of course, the patches (to other files than the crypt/ subdirectory) may
still clash due to changes that are unrelated to the crypto changes. That
is unavoidable, and you'll just have to fix that up by hand.
Linus
-
: 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