Re: Mercurial 0.4b vs git patchbomb benchmark

From: Linus Torvalds <torvalds@osdl.org>
Date: Apr 29, 2005, 19:50 UTC
Message-ID: <Pine.LNX.4.58.0504291248210.18901@ppc970.osdl.org>
In-Reply-To: <20050429191207.GX21897@waste.org>

On Fri, 29 Apr 2005, Matt Mackall wrote:

> 
> Here's an excerpt from http://selenic.com/mercurial/notes.txt on how
> the back-end works.

Any notes on how you maintain repository-level information?

For example, the expense in BK wasn't the single-file history, it was the _repository_ history, ie the "ChangeSet" file. Which grows quite slowly, but because it _always_ grows, it ends up being quite big and expensive to parse after three years.

Ie do you have the git kind of "independent trees/commits", or do you create a revision history of those too?

		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.