git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] git reflog show

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 23, 2006, 14:53 UTC
Message-ID
<Pine.LNX.4.63.0612231552140.19693@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<7v4prmsxjl.fsf@assigned-by-dhcp.cox.net>
Hi,
On Sat, 23 Dec 2006, Junio C Hamano wrote:
Show 15 quoted lines
> 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.

I wonder if it would make sense to teach the revision walking machinery about reflogs. A commit could be marked as coming from a reflog entry, and in that case the parents could be determined by the reflog rather than the commit itself.

Is this a stupid idea?

Ciao, Dscho

Previous: Junio C HamanoNext: Shawn Pearce
Message 3 of 14 in “[RFC] git reflog show”
  1. Shawn PearceDec 23, 2006
  2. Junio C HamanoDec 23, 2006
  3. Johannes SchindelinDec 23, 2006
  4. Shawn PearceDec 24, 2006
  5. Johannes SchindelinDec 24, 2006
  6. Junio C HamanoDec 24, 2006
  7. Johannes SchindelinDec 25, 2006
  8. Junio C HamanoDec 25, 2006
  9. Shawn PearceDec 26, 2006
  10. Junio C HamanoDec 26, 2006
  11. Johannes SchindelinDec 26, 2006
  12. Junio C HamanoDec 26, 2006
  13. Johannes SchindelinDec 26, 2006
  14. Junio C HamanoDec 26, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.