All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Francis Moreau <francis.moro@gmail.com>
Cc: Mike Hommey <mh@glandium.org>, 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 13:05:04 -0400	[thread overview]
Message-ID: <20070827170504.GH4680@thunk.org> (raw)
In-Reply-To: <38b2ab8a0708270621l63f3da56j4667014e62a5de92@mail.gmail.com>

On Mon, Aug 27, 2007 at 03:21:32PM +0200, Francis Moreau wrote:
> This "inconsistency" had already been raised before. Please refer to:
> http://www.gelato.unsw.edu.au/archives/git/0612/35354.html

That's not a major inconsistency problem IMHO because git diff does
not take a set of commits, but rather two end points --- conceptually,
there's no way to make sense out of trying to feed an arbitrary set of
commitments to git-diff.

The bigger inconsistency is with git-format-patch, which *does* take a
set of commits, and where "git-format-patch a" does operates on a very
different set of commits than what what "git-rev-list a" returns.  I
understand that for backwards compatibility "git-format-patch a" is
equivalent to "git-format-patch a..HEAD", but what it means is that
all other ways of specifying sets of commits work with
git-format-patch, *except* if you want to specify all commits from the
beginning of time to a particular head (i.e., "git-rev-list a") is
something that you simply can not possibly do using git-format-patch.
This was mentioned on a blog entry as one of those "really confusing
inconsistencies" in git.

						- Ted

  parent reply	other threads:[~2007-08-27 17:05 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
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 [this message]
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=20070827170504.GH4680@thunk.org \
    --to=tytso@mit.edu \
    --cc=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 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.