From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jari Aalto <jari.aalto@cante.net>, git@vger.kernel.org
Subject: Re: git-rev-parse(1) questions
Date: Mon, 30 Apr 2007 13:20:35 -0700 [thread overview]
Message-ID: <7vejm1d370.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <alpine.LFD.0.98.0704301138320.3419@woody.linux-foundation.org> (Linus Torvalds's message of "Mon, 30 Apr 2007 11:49:06 -0700 (PDT)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Mon, 30 Apr 2007, Jari Aalto wrote:
>> ...
>> * A colon, optionally followed by a stage number (0 to 3) and a
>> colon, followed by a path; this names a blob object in the index
>> at the given path. Missing stage number (and the colon that
>> follows it) names an stage 0 entry.
>
> You'd never use this unless you're working with a unmerged tree entry, and
> then you can use it for things like
>
> git diff :1:my-path :2:their-path
>
> if you want to look at the differences between the two blobs that are
> unmerged, and come from different branches (":1:my-path" comes from the
> branch you were merging things into,and the ":2:their-path" comes from the
> branch you were merging from).
>
> That can be useful in the extremely rare case...
A small correction. :1:path comes from the common ancestor,
:2:mine comes from the branch you are on and merging into, and
:3:theirs is what the other branch you were merging from has.
People can see how rarely this is used interactively; even
original authors of git can get it wrong ;-).
next prev parent reply other threads:[~2007-04-30 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 18:24 git-rev-parse(1) questions Jari Aalto
2007-04-30 18:49 ` Linus Torvalds
2007-04-30 20:20 ` Junio C Hamano [this message]
2007-04-30 18:51 ` Johannes Schindelin
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=7vejm1d370.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
--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.