From: Junio C Hamano <junkio@cox.net>
To: Aneesh Kumar <aneesh.kumar@gmail.com>
Cc: Dave Jones <davej@redhat.com>, git@vger.kernel.org, junkio@cox.net
Subject: Re: [Announce] gitview-0.1
Date: Wed, 01 Feb 2006 12:01:36 -0800 [thread overview]
Message-ID: <7v3bj2df1b.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <cc723f590602010328w7b4a7befr40a76620e197d00c@mail.gmail.com> (Aneesh Kumar's message of "Wed, 1 Feb 2006 16:58:32 +0530")
Aneesh Kumar <aneesh.kumar@gmail.com> writes:
> for parent_id in parent_sha1 parent_sha2 parent_sha3 .......
> commit_diff = commit_diff + git diff tree -p parent_id commit_sha1
>
> is this the correct way ?
Are parent_sha$N true parents of commit_sha1? If you want to
get three independent diffs, "git diff-tree -m -p $commit_sha1"
would give that to you in one go.
next prev parent reply other threads:[~2006-02-01 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 4:16 [Announce] gitview-0.1 Aneesh Kumar
2006-02-01 4:29 ` Dave Jones
2006-02-01 4:41 ` Aneesh Kumar
2006-02-01 11:28 ` Aneesh Kumar
2006-02-01 20:01 ` Junio C Hamano [this message]
2006-02-01 20:17 ` Linus Torvalds
2006-02-01 20:34 ` Junio C Hamano
2006-02-01 20:58 ` Alex Riesen
2006-02-01 21:02 ` Fernando J. Pereda
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=7v3bj2df1b.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=aneesh.kumar@gmail.com \
--cc=davej@redhat.com \
--cc=git@vger.kernel.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.