Messages in this thread | | | Date | Fri, 29 Apr 2005 12:50:55 -0700 (PDT) | From | Linus Torvalds <> | Subject | Re: Mercurial 0.4b vs git patchbomb benchmark |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |