From: Rogan Dawes <lists@dawes.za.net>
To: Matthew L Foster <mfoster167@yahoo.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: merge time
Date: Mon, 30 Jul 2007 18:25:36 +0200 [thread overview]
Message-ID: <46AE1100.2020005@dawes.za.net> (raw)
In-Reply-To: <78813.86273.qm@web51002.mail.re2.yahoo.com>
Matthew L Foster wrote:
> Maybe I am the only one that thinks the web interface should be just as feature rich as the
> command line interface?
>
> -Matt
>
Well, having said that "Use reflogs" was the general response, I don't
think that anyone ever really followed through and made it a readily
accessible feature, even on the command line.
That is, the reflogs are readily accessible, but noone made it possible
to link them to the commits in such a way that the dates/times change as
you seem to desire.
Of course, you can do things like:
$ git show HEAD@{2.days.ago}
to see what HEAD looked like 2 days ago, but you can't do things like
get gitk to show you that this tag only appeared in your repo 2 days ago.
(Keep in mind, of course, that reflogs are referring to YOUR local copy
of the git repo, not what HEAD was on the server that you cloned from.)
And also keep in mind that on the command line you can invoke a lot of
"plumbing commands" that you certainly wouldn't expect to be exposed in
a web interface.
Rogan
next prev parent reply other threads:[~2007-07-30 16:27 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 17:33 merge time Matthew L Foster
2007-07-29 23:19 ` Jakub Narebski
2007-07-29 23:35 ` Linus Torvalds
2007-07-30 1:11 ` Matthew L Foster
2007-07-30 1:27 ` david
2007-07-30 2:29 ` Linus Torvalds
2007-07-30 2:43 ` Matthew L Foster
2007-07-30 3:06 ` Linus Torvalds
2007-07-30 3:16 ` Linus Torvalds
2007-07-30 4:13 ` Matthew L Foster
2007-07-30 11:33 ` Sean
2007-07-30 3:57 ` Matthew L Foster
2007-07-30 6:10 ` Steffen Prohaska
2007-07-30 6:48 ` Junio C Hamano
2007-07-30 7:44 ` Steffen Prohaska
2007-07-30 7:49 ` Shawn O. Pearce
2007-07-30 8:09 ` Steffen Prohaska
2007-07-30 8:14 ` Jeff King
2007-07-30 8:24 ` Junio C Hamano
2007-07-30 8:31 ` Jeff King
2007-07-30 8:25 ` Steffen Prohaska
2007-07-30 8:32 ` Jeff King
2007-07-30 8:34 ` david
2007-07-30 8:41 ` Jeff King
2007-07-30 17:42 ` Linus Torvalds
2007-07-31 18:06 ` Steffen Prohaska
2007-07-31 20:07 ` david
2007-07-30 12:44 ` Rogan Dawes
2007-07-30 16:14 ` Matthew L Foster
2007-07-30 16:20 ` Johannes Schindelin
2007-07-30 16:24 ` Matthew L Foster
2007-07-30 16:25 ` Rogan Dawes [this message]
2007-07-30 17:06 ` Matthew L Foster
2007-07-30 17:13 ` david
2007-07-30 21:57 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2007-07-30 2:28 Matthew L Foster
2007-07-30 3:09 ` Linus Torvalds
2007-07-30 4:10 ` Matthew L Foster
2007-07-30 4:17 ` david
2007-07-30 16:20 ` Matthew L Foster
2007-07-30 16:23 ` david
2007-07-30 17:11 ` Matthew L Foster
2007-07-30 17:33 ` david
2007-07-30 22:11 ` Robin Rosenberg
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=46AE1100.2020005@dawes.za.net \
--to=lists@dawes.za.net \
--cc=git@vger.kernel.org \
--cc=mfoster167@yahoo.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 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).