All of lore.kernel.org
 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: [RFC] git reflog show
Date: Sat, 23 Dec 2006 02:42:54 -0800	[thread overview]
Message-ID: <7v4prmsxjl.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20061223101956.GD9396@spearce.org> (Shawn Pearce's message of "Sat, 23 Dec 2006 05:19:56 -0500")

Shawn Pearce <spearce@spearce.org> writes:

> I'm toying with what a 'git reflog show' might look like.  I attached
> the prototype code below.  Here's the output from the recent part of
> my mmap pack window topic:
>
>   $ ./git-reflog show refs/heads/sp/mapwin
>   ...clipped for space...
>   

The output should look almost the same as "git log" for the part
that represents a series of normal branch activity where commits
are built up one-by-one.  I think it would be useful if you can
somehow make parts that are _not_ linear stand out and perhaps
allow omitting a stretch of ordinary single strand of pearls.

  reply	other threads:[~2006-12-23 10:42 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 [this message]
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
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=7v4prmsxjl.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 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.