From: Andrew Morton <akpm@linux-foundation.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, git@vger.kernel.org
Subject: Re: my git problem
Date: Mon, 28 Apr 2008 12:09:17 -0700 [thread overview]
Message-ID: <20080428120917.dd9f01e8.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0804281948270.19187@eeepc-johanness>
On Mon, 28 Apr 2008 19:49:28 +0100 (BST) Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Mon, 28 Apr 2008, Andrew Morton wrote:
>
> > hm, weirdness.
> >
> > y:/usr/src/git26> git-diff origin...git-ia64
> > y:/usr/src/git26> git-log origin...git-ia64 | wc -l
> > 15574
> >
> > I'd have expected git-log to operate on the same patches as git-diff.
> >
> > I'm sure there's a logical explanation for this ;)
>
> Yes. git-diff with "..." will show you the diff of git-ia64 since the
> branch point, whereas log will show you _all_ the logs (both in origin and
> in git-ia64) since the branch point.
>
That's missing the "logical" bit :)
Oh well. Can you suggest how I can extract the changelogs for the patches
which `git-diff origin...git-ia64' will print out?
Thanks.
next prev parent reply other threads:[~2008-04-28 19:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 18:29 my git problem Andrew Morton
2008-04-27 19:15 ` Linus Torvalds
2008-04-27 19:44 ` Andrew Morton
2008-04-27 20:24 ` Linus Torvalds
2008-04-28 18:45 ` Andrew Morton
2008-04-28 18:49 ` Johannes Schindelin
2008-04-28 19:09 ` Andrew Morton [this message]
2008-04-28 19:13 ` Johannes Schindelin
2008-04-28 19:28 ` Linus Torvalds
2008-04-29 17:15 ` J. Bruce Fields
2008-04-30 8:17 ` Jakub Narebski
2008-04-28 19:33 ` Andrew Morton
2008-04-28 19:21 ` Linus Torvalds
2008-04-28 19:54 ` Andrew Morton
2008-05-01 6:01 ` Carl Worth
2008-04-28 19:52 ` Daniel Barkalow
2008-04-28 21:35 ` Andrew Morton
2008-04-28 21:47 ` Linus Torvalds
2008-04-28 22:04 ` Johannes Schindelin
2008-04-28 22:14 ` Linus Torvalds
2008-04-29 2:14 ` Andrew Morton
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=20080428120917.dd9f01e8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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.