From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Petr Baudis <pasky@suse.cz>, Pavel Roskin <proski@gnu.org>,
git <git@vger.kernel.org>
Subject: Re: Joining cg-*-id
Date: Mon, 19 Sep 2005 22:52:27 -0700 [thread overview]
Message-ID: <7vy85s9tgk.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0509191505470.2553@g5.osdl.org> (Linus Torvalds's message of "Mon, 19 Sep 2005 15:16:03 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> That lack of sha1 completion is a bug.
>
> How does the date thing work? It sounds like something horribly ambiguous,
> but hey, maybe some useful semantics could be found.
I am not even sure what I would want to see, let alone what I
could show, when I say "show logs of what happened last week",
after I just pulled from a remote or two.
I would imagine a gitk graph with nodes colored red for commits
with last week's timestamps, would be what I would want, but
probably that is useful only because I can see in the same gitk
window how those red nodes connect with each other and with
commits outside the specified time window. Without that context
information I would probably be lost.
> The short sha1 problem is fixed thus,
Thanks. Applied.
next prev parent reply other threads:[~2005-09-20 5:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 21:40 Joining cg-*-id Pavel Roskin
2005-09-19 21:56 ` Petr Baudis
2005-09-19 22:16 ` Linus Torvalds
2005-09-19 22:54 ` Petr Baudis
2005-09-20 0:50 ` Linus Torvalds
2005-09-20 13:57 ` Petr Baudis
2005-09-20 14:53 ` Linus Torvalds
2005-09-20 15:07 ` Petr Baudis
2005-09-20 16:54 ` Linus Torvalds
2005-09-20 19:34 ` Linus Torvalds
2005-09-21 10:35 ` Paul Mackerras
2005-09-21 14:51 ` Linus Torvalds
2005-09-21 21:19 ` Paul Mackerras
2005-09-21 8:50 ` Petr Baudis
2005-09-20 15:13 ` Matthias Urlichs
2005-09-20 5:52 ` Junio C Hamano [this message]
2005-09-20 10:11 ` Matthias Urlichs
2005-09-20 12:32 ` Paul Mackerras
2005-09-19 22:30 ` Pavel Roskin
2005-09-19 22:58 ` Petr Baudis
2005-09-20 0:19 ` Pavel Roskin
2005-09-20 0:26 ` Petr Baudis
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=7vy85s9tgk.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=proski@gnu.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 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).