All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Ludvig <michal@logix.cz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	linux-crypto@vger.kernel.org, git@vger.kernel.org
Subject: Re: Creating diff from 2.6.16 from cryptodev-2.6 git tree
Date: Fri, 30 Jun 2006 17:45:17 +1200	[thread overview]
Message-ID: <44A4BA6D.5010006@logix.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0606291943010.12404@g5.osdl.org>

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?

As it is the patch conflicts on files that were changed multiple times
since 2.6.16 :-(

Will see if patchutils can help me somehow...

Michal

  parent reply	other threads:[~2006-06-30  5:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-30  1:18 Creating diff from 2.6.16 from cryptodev-2.6 git tree Michal Ludvig
2006-06-30  1:36 ` Herbert Xu
2006-06-30  2:25   ` Linus Torvalds
2006-06-30  2:32     ` Herbert Xu
2006-06-30  2:44       ` Linus Torvalds
2006-06-30  3:05         ` Michal Ludvig
2006-06-30  5:45         ` Michal Ludvig [this message]
2006-06-30  6:20           ` Linus Torvalds
2006-06-30  6:28           ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44A4BA6D.5010006@logix.cz \
    --to=michal@logix.cz \
    --cc=git@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.