From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 13 Feb 2014 22:50:36 GMT
Subject: Re: Git GSoC 2014
Message-ID: <xmqqk3cyk4oz.fsf@gitster.dls.corp.google.com>
In-Reply-To: <87bnya8z6q.fsf@thomasrast.ch>

Thomas Rast <tr@thomasrast.ch> writes:

> Downside: not listing "code merged" as a goal may not make the project
> as shiny, neither for Git nor for the student.

I'd actually view that as an upside. This sounds like a good first
step for a feasibility study that is really necessary.

I wonder why the handling of storage corruption and replacement
could be left broken, though. Is that because libgit2 has known
breakages in these areas, or is there some other reason?