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