Re: epic fsck SIGSEGV!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 10 Dec 2008, Junio C Hamano wrote:

> Nicolas Pitre <nico@xxxxxxx> writes:
> 
> > On Wed, 10 Dec 2008, Linus Torvalds wrote:
> >
> >> But we should definitely fix this braindamage in fsck. Rather than 
> >> recursively walk the commits, we should add them to a commit list and just 
> >> walk the list iteratively.
> >
> > What about:
> >
> > 	http://marc.info/?l=git&m=122889563424786&w=2
> 
> I have to dig that out of the mail archive (quoting message-id or $gmane
> article number would have been easier for me),

Message-ID: <20081210075338.GA7776@xxxxxxxxxxxxxxxxx>

> but should I take it as an Ack from you?

I was involved in that thread initially, until bisection showed commit 
271b8d25b25e49b367087440e093e755e5f35aa9 as the culprit.  This might be 
the same issue but I have not experienced it myself.

So I'm merely only connecting email threads here.


Nicolas
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux