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: Thu, 01 Jun 2006 23:40:43 -0700 [thread overview]
Message-ID: <7v3beodpqs.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20060602023545.GA5039@spearce.org
Shawn Pearce <spearce@spearce.org> writes:
> I find it useful to track what I've sent to you just in case I
> screw up some ref somewhere. I like knowing that if I perform a
> bad update-ref call (which I'm prone to do sometimes) that I can
> recover quickly as the log exists.
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
Wed May 31 14:26:39 2006 -0700
422dfaf... Merge branch 'lt/tree-2' into next
Wed May 31 15:14:58 2006 -0700
100c25f... Merge branch 'ff/svnimport' into next
Wed May 31 15:23:54 2006 -0700
a25963b... Merge branch 'jc/fmt-patch' into next
...
The latter is probably not so useful in practice -- I suspect
that I would want to see such a list only while I am interested
in how well reflog works.
next prev parent reply other threads:[~2006-06-02 6:40 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 [this message]
2006-06-06 5:39 ` Shawn Pearce
2006-06-06 6:16 ` Junio C Hamano
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=7v3beodpqs.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).