git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: What's in git.git (part #2)
Date: Mon, 05 Jun 2006 23:16:50 -0700	[thread overview]
Message-ID: <7vhd2yzu3x.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060606053905.GA9797@spearce.org> (Shawn Pearce's message of "Tue, 6 Jun 2006 01:39:05 -0400")

Shawn Pearce <spearce@spearce.org> writes:

>> I find it interesting to be able to say:
>> 
>> 	$ git log next@{yesterday}..next
>> 
>> I often find myself getting curious to see:
>> 
>> 	$ git reflog next
>>         Wed May 31 14:23:58 2006 -0700
>>                 62b693a... Merge branch 'master' into next
>>         ...
>
> Hmm, looks like nobody has actually implemented that - at least not
> in 'next'.  :-)
>
> Is that a serious feature request?

I've written it but it was so trivial I threw it away after
writing the e-mail you are responding to with it.

As I said, I _think_ I was interested in seeing it primarily
because reflog was a new curiosity to me.  It is more like
wanting to know how the new tool works more than using the new
tool effectively to improve my productivity.  In a "serious"
environment, a tool is just something you would use to get the
real job done, not to toy around to see how _it_ works, so I
suspect the above would not be so useful in practice, as I wrote
in the message.

  reply	other threads:[~2006-06-06  6:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01  9:19 What's in git.git (part #2) Junio C Hamano
2006-06-01  9:23 ` Junio C Hamano
2006-06-01  9:31   ` Jakub Narebski
     [not found] ` <20060601072637.9920c8c5.seanlkml@sympatico.ca>
2006-06-01 11:26   ` Sean
2006-06-01 22:51 ` Ryan Anderson
2006-06-02  2:35 ` Shawn Pearce
2006-06-02  6:40   ` Junio C Hamano
2006-06-06  5:39     ` Shawn Pearce
2006-06-06  6:16       ` Junio C Hamano [this message]
2006-06-06  8:19       ` 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=7vhd2yzu3x.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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).