From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Christian Couder <christian.couder@gmail.com>
Cc: Jeff King <peff@peff.net>, git <git@vger.kernel.org>
Subject: Re: [RFH] hackday and GSoC topic suggestions
Date: Thu, 06 Feb 2014 10:51:54 +0100 [thread overview]
Message-ID: <vpqr47gin5x.fsf@anie.imag.fr> (raw)
In-Reply-To: <CAP8UFD1B+108EyyhFQh6RnVVpOUCLiK+oNPONrNJqkNftLFYLA@mail.gmail.com> (Christian Couder's message of "Thu, 6 Feb 2014 10:10:05 +0100")
Christian Couder <christian.couder@gmail.com> writes:
> I would be interested in mentoring a GSoC student working on the "git
> bisect fix/unfixed" feature.
Interestingly, I used the feature in real-life last week, and had to
think upside-down to type the right "good"/"bad" keywords ;-).
> 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.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2014-02-06 9:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 22:57 [RFH] hackday and GSoC topic suggestions Jeff King
2014-02-06 9:10 ` Christian Couder
2014-02-06 9:51 ` Matthieu Moy [this message]
2014-02-13 8:50 ` Jeff King
2014-02-13 9:28 ` Christian Couder
2014-02-13 9:55 ` David Kastrup
2014-02-08 18:43 ` Thomas Rast
2014-02-08 18:55 ` Jeff King
2014-02-08 19:03 ` Thomas Rast
2014-02-16 14:42 ` Duy Nguyen
2014-02-16 15:29 ` Thomas Rast
2014-02-11 18:57 ` Junio C Hamano
2014-02-11 19:38 ` Junio C Hamano
2014-02-13 8:37 ` Jeff King
2014-02-13 8:41 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpqr47gin5x.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.