From: Junio C Hamano <junkio@cox.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [RFC] git reflog show
Date: Mon, 25 Dec 2006 22:14:23 -0800 [thread overview]
Message-ID: <7vd567fakg.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20061226054815.GC28084@spearce.org> (Shawn Pearce's message of "Tue, 26 Dec 2006 00:48:15 -0500")
Shawn Pearce <spearce@spearce.org> writes:
> So what you are proposing is to make the reflog visible in 'git log'
> by a new option? Or to just try to reuse all of its display code
> but keep the reflog under 'git reflog show' ?
I am not specifically proposing anything, but the part you
quoted is about the latter.
What Johannes brought up would involve hooking into the usual
log walking machinery to show the commits in "merge order" (more
precisely, "local appearance order"). I do not think it is
about "showing the reflog data", but about using reflog data to
give a different presentation order to the usual log output.
Your "reflog show" is more about showing what are recorded in
the reflog.
It is not like implementing the sorting of the logs in local
appearance order would make your "reflog show" redundant or
useless; both are independently useful, I think.
next prev parent reply other threads:[~2006-12-26 6:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-23 10:19 [RFC] git reflog show Shawn Pearce
2006-12-23 10:42 ` Junio C Hamano
2006-12-23 14:53 ` Johannes Schindelin
2006-12-24 6:11 ` Shawn Pearce
2006-12-24 12:49 ` Johannes Schindelin
2006-12-24 21:47 ` Junio C Hamano
2006-12-25 14:01 ` Johannes Schindelin
2006-12-25 18:07 ` Junio C Hamano
2006-12-26 5:48 ` Shawn Pearce
2006-12-26 6:14 ` Junio C Hamano [this message]
2006-12-26 16:14 ` Johannes Schindelin
2006-12-26 19:03 ` Junio C Hamano
2006-12-26 23:20 ` Johannes Schindelin
2006-12-26 23:50 ` Junio C Hamano
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=7vd567fakg.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--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 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.