On Thu, Feb 13, 2014 at 9:50 AM, Jeff King <peff@xxxxxxxx> wrote: > On Thu, Feb 06, 2014 at 10:51:54AM +0100, Matthieu Moy wrote: > >> > Some of Matthieu's students worked on it a few years ago but didn't finish. >> >> Right. There was still quite some work to do, but this is most likely >> too small for a GSoC project. But that could be a part of it. I'm not >> sure how google welcomes GSoC projects made of multiple small tasks, but >> my experience with students is that it's much better than a single (too) >> big task, and I think that was the general feeling on this list when we >> discussed it last year. > > I think Google leaves it up to us to decide. I'd be OK with a project > made of multiple small tasks, as I think it would be an interesting > experiment. I'd rather not do all of them like that, though. And bonus > points if they are on a theme that will let the student use the ramp-up > time from one for another. Yeah, a student working on the "git bisect fix/unfixed" feature, could fix git bisect testing too many merge bases, and if there is still time work on moving more code from shell to C. -- 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