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 25, 2006, 14:01 UTC
Message-ID
<Pine.LNX.4.63.0612251449140.19693@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<7v1wmpq83g.fsf@assigned-by-dhcp.cox.net>
Hi,
On Sun, 24 Dec 2006, Junio C Hamano wrote:
Show 10 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > Yes, but if we have to read the reflog anyway to determine the logical 
> > (local) parent, we can just as well read the message, and display it, 
> > too.
> >
> > What it buys us is that we do not duplicate efforts here, and we can 
> > easily visualize the reflog in gitk, too.
> 
> I do not think you can sanely rewrite parenthood.

Well, I did not mean to change the parents in the commit object. Rather, let the revision walker determine the parent differently for reflogs.

> Also I highly doubt visualization based on parents information rewritten 
> to match the reflog order is of _any_ use.  By rewriting the parenthood, 
> you are losing the topology and your visualization is no better than 
> what "tac .git/logs/$ref" would give.

Okay, but if they are _not_ rewritten, we can reuse the log machinery to show the revisions in "upstream..master@{2.hours.ago}", but in the order they came into the local repository.

Ciao, Dscho

Previous: Junio C HamanoNext: Junio C Hamano
Message 7 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.