Re: Fast access git-rev-list output: some OS knowledge required
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Dec 6, 2006, 23:27 UTC
- Message-ID
- <Pine.LNX.4.63.0612070025450.28348@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <20061206192800.GC20320@spearce.org>
Hi,
On Wed, 6 Dec 2006, Shawn Pearce wrote:
Show 10 quoted lines
> Marco Costalba <mcostalba@gmail.com> wrote: > > The time it takes to read, without processing, the whole Linux tree > > with this approach it's almost _double_ of the time it takes 'git > > rev-list' to write to a file: > > > > 3) Other suggestions? ;-) > > The revision listing machinery is fairly well isolated behind some > pretty clean APIs in Git. Why not link qgit against libgit.a and just > do the revision listing in process?
Because, depending on what you do, the revision machinery is not reentrable. For example, if you filter by filename, the history is rewritten in-memory to simulate a history where just that filename was tracked, and nothing else. These changes are not cleaned up after calling the internal revision machinery.
Hth, Dscho