git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Jakub Narebski <jnareb@gmail.com>
Cc: "Alejandro Riveira Fernández" <ariveira@gmail.com>,
	"Randy Dunlap" <rdunlap@xenotime.net>, Andy <genanr@emsphone.com>,
	linux-kernel@vger.kernel.org, git@vger.kernel.org
Subject: Re: How can I download a git commit as a diff patch?
Date: Wed, 30 Sep 2009 17:07:46 -0400	[thread overview]
Message-ID: <20090930210745.GC22159@csclub.uwaterloo.ca> (raw)
In-Reply-To: <200909302240.17729.jnareb@gmail.com>

On Wed, Sep 30, 2009 at 10:40:16PM +0200, Jakub Narebski wrote:
> You can specify parent explicitely: "git diff <rev>^1 <rev>" for diff
> to first parent, e.g. "git diff HEAD^ HEAD".
> 
> Just so you know that this single diff is not enough to redo a merge.
> It is only partial information.

Yes certainly in some cases.  Often you can pick specific patches and
a few patches they depend on to try and fix something, but for bigger
changes it doesn't work.  I am actually surprised it has been this long
before I ever saw one of these combined diff's.  I must have been lucky
so far.

> BTW. there is also "git diff-tree -m <rev>") to show diff to *all*
> parents at once:
> 
>     -m    By default, `git-diff-tree --stdin` does not show differences for
>           merge commits. With this flag, it shows differences to that commit
>           from all of its parents. See also `-c`.

I will have to try that one out.

-- 
Len Sorensen

      reply	other threads:[~2009-09-30 21:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090930154410.GA31502@thumper2>
     [not found] ` <20090930085500.a5856301.rdunlap@xenotime.net>
     [not found]   ` <20090930190014.GA22161@csclub.uwaterloo.ca>
2009-09-30 19:38     ` How can I download a git commit as a diff patch? Alejandro Riveira Fernández
2009-09-30 20:10       ` Jakub Narebski
2009-09-30 20:25         ` Lennart Sorensen
2009-09-30 20:40           ` Jakub Narebski
2009-09-30 21:07             ` Lennart Sorensen [this message]

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=20090930210745.GC22159@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=ariveira@gmail.com \
    --cc=genanr@emsphone.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).