From: Shawn Pearce <spearce@spearce.org>
To: git@vger.kernel.org
Subject: Re: [PATCH] annotate: Support annotation of files on other revisions.
Date: Mon, 6 Mar 2006 01:32:54 -0500 [thread overview]
Message-ID: <20060306063254.GE26820@spearce.org> (raw)
In-Reply-To: <7vpsl0ayij.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> Shawn Pearce <spearce@spearce.org> writes:
>
> > git-diff Makefile
> > git-diff HEAD Makefile
> >
> > ? (Which is rather ugly as what if you have a tracked file actually
> > called HEAD and you want the first form when the commit-ish is
> > omitted.) So accepting an optional commit-ish before the filename
> > would be in line with what git-diff accepts today.
>
> The use of "start of filelist" marker "--" is optional when
> unambiguous, and that is why "git-diff Makefile" works. To view
> the change you still haven't update-index'ed to the path called
> "HEAD", you would naturally say "git-diff -- HEAD"
Naturally. :-)
After getting along fine with `git-diff foo` for months I would
natually not be surprised when `git-diff foo` didn't work because
I performed a `git-checkout -b foo pu` one day.
--
Shawn.
next prev parent reply other threads:[~2006-03-06 6:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 11:13 [PATCH] git-blame: Use the same tests for git-blame as for git-annotate Fredrik Kuivinen
2006-03-05 23:32 ` Ryan Anderson
2006-03-06 0:19 ` Junio C Hamano
2006-03-06 0:29 ` Martin Langhoff
2006-03-06 2:43 ` [PATCH] annotate: Support annotation of files on other revisions Ryan Anderson
2006-03-06 4:18 ` Martin Langhoff
2006-03-06 7:49 ` Fredrik Kuivinen
2006-03-06 5:31 ` A Large Angry SCM
2006-03-06 5:40 ` Ryan Anderson
2006-03-06 5:50 ` Shawn Pearce
2006-03-06 6:16 ` Junio C Hamano
2006-03-06 6:32 ` Shawn Pearce [this message]
2006-03-06 6:21 ` A Large Angry SCM
2006-03-06 6:28 ` Junio C Hamano
2006-03-06 9:24 ` Johannes Schindelin
2006-03-06 9:18 ` Johannes Schindelin
2006-03-06 15:44 ` Ryan Anderson
2006-03-06 2:56 ` [PATCH] git-blame: Use the same tests for git-blame as for git-annotate Ryan Anderson
2006-03-06 6:12 ` [PATCH] annotate/blame tests updates Junio C Hamano
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=20060306063254.GE26820@spearce.org \
--to=spearce@spearce.org \
--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 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).