From: Mike Hommey <mh@glandium.org>
To: Shawn Bohrer <shawn.bohrer@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Confusion about diffing branches
Date: Mon, 27 Aug 2007 08:25:08 +0200 [thread overview]
Message-ID: <20070827062508.GA9002@glandium.org> (raw)
In-Reply-To: <20070827014056.GB7422@mediacenter.austin.rr.com>
On Sun, Aug 26, 2007 at 08:40:56PM -0500, Shawn Bohrer <shawn.bohrer@gmail.com> wrote:
> So if I understand you correctly people in the git world are simply more
> used to typing two dots (instead of three) so that is why the two dot
> notation shows the more common use case (show me the difference between
> the tip of the master branch and the tip of the topic branch).
>
> I must admit that for me, a new git user, it would be much more
> intuitive if all git commands used the same syntax for specifying
> revisions. After all every other git command that I have used so far
> uses the opposite syntax as git-diff. This includes git-log,
> git-format-patch, gitk, git-rev-list, and git-rev-parse.
Similar experience here. It is even more a problem for newcomers when
you consider it isn't documented in either git-rev-parse or git-diff
manual pages.
Mike
next prev parent reply other threads:[~2007-08-27 6:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 23:35 Confusion about diffing branches Shawn Bohrer
2007-08-27 0:18 ` Junio C Hamano
2007-08-27 1:40 ` Shawn Bohrer
2007-08-27 6:25 ` Mike Hommey [this message]
2007-08-27 7:07 ` Junio C Hamano
2007-08-27 7:50 ` Mike Hommey
2007-08-27 13:21 ` Francis Moreau
2007-08-27 13:33 ` Mike Hommey
2007-08-27 17:06 ` Junio C Hamano
2007-08-27 17:24 ` Mike Hommey
2007-08-27 17:05 ` Theodore Tso
2007-08-27 17:20 ` Junio C Hamano
2007-08-27 20:29 ` Theodore Tso
2007-08-27 22:20 ` Jakub Narebski
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=20070827062508.GA9002@glandium.org \
--to=mh@glandium.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=shawn.bohrer@gmail.com \
/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).