From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] (preview) Renaming push.
Date: Thu, 04 Aug 2005 01:09:10 -0700 [thread overview]
Message-ID: <7vvf2m2kex.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0508032236470.3258@g5.osdl.org> (Linus Torvalds's message of "Wed, 3 Aug 2005 22:42:06 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> Now, for extra bonus points, maybe you should make "git-rev-list" also
> understand the "rev..rev" format (which you can't do with just the
> get_sha1() interface, since it expands into more).
Hmph. That makes sense.
What I set out to do when I started ripping extended_sha1 out of
rev-parse was actually something else.
Remember I was stupidly wondering why "git log master..gitk" did
not do what I wanted to?
The reason I started looking at git-rev-parse was because I
wanted to add "git log master...gitk" (three dots) which is
equivalent to "git log $(git-merge-base master gitk)..gitk".
That was what I wanted to have when I asked that stupid
question.
But unfortunately my GIT day this week is over, so the rest is
for the weekend.
next prev parent reply other threads:[~2005-08-04 8:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 23:10 Users of git-check-files? Johannes Schindelin
2005-08-03 2:43 ` Linus Torvalds
2005-08-03 6:17 ` Junio C Hamano
2005-08-03 14:21 ` Johannes Schindelin
2005-08-03 18:00 ` Linus Torvalds
2005-08-03 22:09 ` Johannes Schindelin
2005-08-03 15:09 ` Linus Torvalds
2005-08-03 15:51 ` Junio C Hamano
2005-08-03 16:17 ` Linus Torvalds
2005-08-03 16:36 ` Junio C Hamano
2005-08-03 16:45 ` Linus Torvalds
2005-08-03 16:50 ` Johannes Schindelin
2005-08-03 17:08 ` Josef Weidendorfer
2005-08-03 17:30 ` Junio C Hamano
2005-08-03 17:46 ` Josef Weidendorfer
2005-08-03 18:08 ` Linus Torvalds
2005-08-03 23:25 ` [PATCH] (preview) Renaming push Junio C Hamano
2005-08-03 23:48 ` Linus Torvalds
2005-08-04 0:05 ` Junio C Hamano
2005-08-04 0:13 ` Linus Torvalds
2005-08-04 1:02 ` Junio C Hamano
2005-08-04 5:26 ` Junio C Hamano
2005-08-04 5:42 ` Linus Torvalds
2005-08-04 8:09 ` Junio C Hamano [this message]
2005-08-04 9:34 ` [PATCH] Teach rev-list since..til notation Junio C Hamano
2005-08-03 18:02 ` Users of git-check-files? Linus Torvalds
2005-08-03 17:02 ` Junio C Hamano
2005-08-03 17:23 ` Linus Torvalds
2005-08-03 17:37 ` Junio C Hamano
2005-08-03 17:46 ` Josef Weidendorfer
2005-08-03 18:10 ` Linus Torvalds
2005-08-03 17:48 ` Linus Torvalds
2005-08-03 18:07 ` Junio C Hamano
2005-08-03 18:31 ` Josef Weidendorfer
2005-08-03 16:46 ` Johannes Schindelin
2005-08-04 20:59 ` Junio C Hamano
2005-08-04 21:10 ` Johannes Schindelin
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=7vvf2m2kex.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--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 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.