From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: a few remaining issues...
Date: Fri, 5 Jan 2007 14:33:06 -0500 [thread overview]
Message-ID: <20070105193306.GB8753@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0701051453520.22628@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Fri, 5 Jan 2007, Junio C Hamano wrote:
>
> > * Reflogs.
> >
> > 'git reflog show' needs to be done -- and preferrably in a way that does
> > not add too much code.
>
> I do not have time to follow up on my earlier attempts to teach git-log
> about traversing reflogs instead of the commit parents. But Shawn had a
> working proposal, didn't he?
Yes, but my proposal added a lot of code. Junio's comment is that
he would prefer one that doesn't, such as by reusing as much of the
revision listing machinary as possible. Which you had looked into
doing.
I myself am also severly lacking in time right now. *if* I get
any more Git time in the next week its going to be to finish out
some patches on the bash-completion, so I can try to sneak them
into the v1.5.0 release (if possible). Its unlikely I'll be able
to look at a `reflog show` anytime soon.
--
Shawn.
next prev parent reply other threads:[~2007-01-05 19:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 11:06 a few remaining issues Junio C Hamano
2007-01-05 11:27 ` Alex Riesen
2007-01-10 12:21 ` Johannes Schindelin
2007-01-10 12:40 ` Alex Riesen
2007-01-10 13:46 ` Johannes Schindelin
2007-01-10 13:56 ` Alex Riesen
2007-01-05 13:55 ` Johannes Schindelin
2007-01-05 19:33 ` Shawn O. Pearce [this message]
2007-01-09 11:21 ` Johannes Schindelin
2007-01-09 20:22 ` Junio C Hamano
2007-01-09 23:53 ` Johannes Schindelin
2007-01-10 0:16 ` Shawn O. Pearce
2007-01-10 1:23 ` Johannes Schindelin
2007-01-05 16:54 ` Juergen Ruehle
2007-01-08 21:59 ` Junio C Hamano
2007-01-08 22:14 ` 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=20070105193306.GB8753@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.