[PATCH] repo.commit not finding new/deleted files

[Matt Mackall]

On Fri, Jun 10, 2005 at 04:54:37PM -0400, Chris Mason wrote:
> > Chris, while you're in there, you might take a stab at fixing up the
> > bit where it tries to create /dev/null when a patch deletes a file.
> > Import needs a few more IQ points.
> 
> I'm thinking about ways to make import faster, even when I disable compression 
> and deltas the best I can get is 3.6 patches/sec (quilt runs at 37 
> patches/sec).  I'm hoping that I can get much better speeds by following your 
> changegroup suggestion.  

What are you measuring with quilt, how quickly it applies patches? How
much did disabling compression and deltas change things?

I've found that the slowest bits tend to be reading/writing the
manifest. Doing this in an extension might be a win. But I'd recommend
trying out the profiler and figuring out exactly what's happening.

Extra credit for adding a -p flag to commands.py to profile a given
command.

I was earlier thinking of breaking up the manifest like git's tree
blobs. But experimentation with git has shown me that's exactly what I
don't want to do: that turns a single manifest read into 1300
directory reads/seeks.

-- 
Mathematics is the supreme nostalgia of our time.