git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Shawn Bohrer <shawn.bohrer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Confusion about diffing branches
Date: Sun, 26 Aug 2007 17:18:35 -0700	[thread overview]
Message-ID: <7v6431omn8.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20070826233555.GA7422@mediacenter.austin.rr.com> (Shawn Bohrer's message of "Sun, 26 Aug 2007 18:35:55 -0500")

Shawn Bohrer <shawn.bohrer@gmail.com> writes:

> So I imagine I'm missing something, or perhaps I'm just looking at this
> from the wrong perspective, but here is what I'm seeing.  Lets say I
> have something like:
>
>          A---B topic
>         /
>    C---D---E master
>
> ...
>    git diff master...topic
>
> ... shows me the
> combined diff of A and B.

That is working as designed.

When you are working on topic it is often desired to see "what
have I done since I forked?" and "what have they done while I
was looking the other way?".

"git diff master topic" (which is the same as "git diff
master..topic" -- the two-dot form is just a syntax sugar to
avoid mistypes for people who are too used to type two dots as
reflex because that is how you express a revision range) shows
a squashed diff that is A+B-E, and often people found "-E" part
distracting and useless.  Three-dot form was invented
specifically to address this problem.  You do not have to (and
you do not _want_ to) use that form if you _want_ to see the -E
part of the diff.

  reply	other threads:[~2007-08-27  0:18 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 [this message]
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
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=7v6431omn8.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.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).