From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
git@vger.kernel.org, Petr Baudis <pasky@ucw.cz>
Subject: Re: Complete http-pull; where should it go?
Date: Sun, 01 May 2005 19:03:28 -0700 [thread overview]
Message-ID: <7v4qdmqt8v.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0505011840590.2162@ppc970.osdl.org> (Linus Torvalds's message of "Sun, 1 May 2005 18:50:13 -0700 (PDT)")
>>>>> "LT" == Linus Torvalds <torvalds@osdl.org> writes:
LT> Hmm.. I actually implemented it, because it's simple to
LT> implement, but now that I've tried using it, I just find it
LT> to be too much like line noise to do
LT> git-diff-tree -p 0-HEAD HEAD
LT> for "parent to current". The notation "-HEAD" also works,
LT> but since that looks like a command line flag, it's usually
LT> not useful, except when combined with other stuff, ie
LT> "0---HEAD" is "three parents up".
That's why I said I do not think this belongs to the Plumbing.
JIT command-line would do just "jit-diff" to get the diff
between the work tree and the commit (or snapshot) it is based
upon, without parameter. Fully spelled out, it would be
"jit-diff -1:1". This kind of syntax, although is quite useful
in JIT context (e.g. saying "jit-patch --2" to mean "apply
changes between snnapshot 2 and two parents up of it to my
current work tree"), I tend to agree that it is a bit too weird
for the core Plumbing layer, for which Unixy syntax is more
suitable.
next prev parent reply other threads:[~2005-05-02 2:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 19:29 Complete http-pull; where should it go? Daniel Barkalow
2005-05-01 19:44 ` Linus Torvalds
2005-05-01 20:30 ` Daniel Barkalow
2005-05-01 20:46 ` Linus Torvalds
2005-05-01 21:25 ` Daniel Barkalow
2005-05-01 23:23 ` Linus Torvalds
2005-05-01 23:46 ` Daniel Barkalow
2005-05-01 23:48 ` Linus Torvalds
2005-05-02 0:09 ` Junio C Hamano
2005-05-02 1:50 ` Linus Torvalds
2005-05-02 2:03 ` Junio C Hamano [this message]
2005-05-02 2:43 ` Linus Torvalds
2005-05-02 2:31 ` Daniel Barkalow
2005-05-01 21:25 ` Junio C Hamano
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=7v4qdmqt8v.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
--cc=torvalds@osdl.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