git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Francis Moreau" <francis.moro@gmail.com>
To: "Mike Hommey" <mh@glandium.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Shawn Bohrer" <shawn.bohrer@gmail.com>,
	git@vger.kernel.org
Subject: Re: Confusion about diffing branches
Date: Mon, 27 Aug 2007 15:21:32 +0200	[thread overview]
Message-ID: <38b2ab8a0708270621l63f3da56j4667014e62a5de92@mail.gmail.com> (raw)
In-Reply-To: <20070827075009.GA31438@glandium.org>

Hi !

On 8/27/07, Mike Hommey <mh@glandium.org> wrote:
> On Mon, Aug 27, 2007 at 12:07:39AM -0700, Junio C Hamano <gitster@pobox.com> wrote:
> > Both semantics of two-dot form and three-dot form are useful,
> > and choice between the two depends on what you want out of the
> > command.  You just need to know which one you want.
>
> The problem is not about usefulness of these 2 forms, but consistency
> with the rest of the tools.
> If I go git log a..b, I won't get the set of commits involved in
> git diff a..b. In fact, git log a...b does. And git log a..b gives the
> commits involved in git diff a...b. Confusing, isn't it ?
> Moreover, this inconsistency isn't even documented in the manual pages.
>

This "inconsistency" had already been raised before. Please refer to:
http://www.gelato.unsw.edu.au/archives/git/0612/35354.html

I shared and still share your feeling about that but it seems that
Junio and Linus don't...

good luck ;)
-- 
Francis

  reply	other threads:[~2007-08-27 13:21 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
2007-08-27  7:07     ` Junio C Hamano
2007-08-27  7:50       ` Mike Hommey
2007-08-27 13:21         ` Francis Moreau [this message]
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=38b2ab8a0708270621l63f3da56j4667014e62a5de92@mail.gmail.com \
    --to=francis.moro@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mh@glandium.org \
    --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).