Hi, On Sun, 24 Dec 2006, Junio C Hamano wrote: > 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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Tue Dec 26 01:02:39 2006
This archive was generated by hypermail 2.1.8 : 2006-12-26 01:04:10 EST