From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Confusion about diffing branches
Date: Tue, 28 Aug 2007 00:20:23 +0200 [thread overview]
Message-ID: <favin5$2sm$1@sea.gmane.org> (raw)
In-Reply-To: 20070827014056.GB7422@mediacenter.austin.rr.com
Shawn Bohrer wrote:
> 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.
git-rev-list, git-log, gitk accepts _range_ of commits. git-diff and
its variants accepts _endpoints_ to compare, with some syntactic sugar
to be able to copy arguments from "git log a..b" to "git diff a..b".
The arguments are just simply different type.
As to git-format-patch, there is matter of backward compatibilty
and ease of use (get last commit as a patch).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2007-08-27 22: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
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 [this message]
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='favin5$2sm$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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).