Re: [PATCH 2/2] Support "history replay" for git log commands

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Nov 2, 2007, 21:17 UTC
Message-ID: <alpine.LFD.0.999.0711021416450.3342@woody.linux-foundation.org>
In-Reply-To: <7v4pg41hq0.fsf@gitster.siamese.dyndns.org>

On Fri, 2 Nov 2007, Junio C Hamano wrote:

Show 5 quoted lines

> 
> Can one iteration of loop in log_tree_commit() smudge more
> than one commits with FORCE_REPLAY?  Maybe make the
> trigger_replay a counter and count down in this loop until we
> find that many commits that have the FORCE_REPLAY flag?

Good point, and yes, that sounds like the right thing to do.

		Linus

$ 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.