On Mon, 2008-01-28 at 22:28 +0000, James Westby wrote:
> Hi,
>
> Thanks for your bug report.
>
> I am interested in what is causing the problem that you are
> seeing. From the traceback I would guess that it is using a
> lot of memory to read the dirstate (the on disk representation
> of the state of the working tree).
Actually, I suspect its a corrupt dirstate; using the non C version of
the dirstate parser will likely work better and give a better message.
On Mon, 2008-01-28 at 22:28 +0000, James Westby wrote:
> Hi,
>
> Thanks for your bug report.
>
> I am interested in what is causing the problem that you are
> seeing. From the traceback I would guess that it is using a
> lot of memory to read the dirstate (the on disk representation
> of the state of the working tree).
Actually, I suspect its a corrupt dirstate; using the non C version of
the dirstate parser will likely work better and give a better message.
-Rob www.robertcolli ns.net/ keys.txt>.
--
GPG key available at: <http://