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
On Thu, Jun 29, 2006 at 07:25:01PM -0700, Linus Torvalds wrote:
The easiest by far is if you only care about a certain sub-directory.
Then, assuming the branch crypto is the top-most commit of the cryptodev
repo, just do
git diff v2.6.16..crypto -- crypto/
Yes, you should always
On Fri, 30 Jun 2006, Herbert Xu wrote:
On Thu, Jun 29, 2006 at 07:25:01PM -0700, Linus Torvalds wrote:
The easiest by far is if you only care about a certain sub-directory.
Then, assuming the branch crypto is the top-most commit of the cryptodev
repo, just do
git diff
Linus Torvalds wrote:
Note that this is why
git log -p --full-diff v2.6.16.. crypto/
is so great. It will show everything that touched that subdirectory, along
with the incidentals. I think that in this case, that's exactly what
Michal wants.
Exactly!
I just want to have the
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
-
To
