From: Junio C Hamano <gitster@pobox.com>
To: Thomas Rast <tr@thomasrast.ch>
Cc: Jeff King <peff@peff.net>,
git@vger.kernel.org, Shawn Pearce <spearce@spearce.org>
Subject: Re: Git GSoC 2014
Date: Thu, 13 Feb 2014 14:50:36 -0800 [thread overview]
Message-ID: <xmqqk3cyk4oz.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <87bnya8z6q.fsf@thomasrast.ch> (Thomas Rast's message of "Thu, 13 Feb 2014 22:45:01 +0100")
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?
next prev parent reply other threads:[~2014-02-13 22:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 9:10 Git GSoC 2014 Jeff King
2014-02-13 21:45 ` Thomas Rast
2014-02-13 22:50 ` Junio C Hamano [this message]
2014-02-14 7:26 ` Thomas Rast
2014-02-14 9:44 ` David Kastrup
2014-02-15 12:17 ` Thomas Rast
2014-02-15 12:35 ` Duy Nguyen
2014-02-15 13:03 ` David Kastrup
2014-02-15 23:47 ` Shawn Pearce
2014-02-14 17:53 ` Vicent Martí
2014-02-13 23:17 ` Ramkumar Ramachandra
2014-02-14 10:41 ` Jeff King
2014-02-14 15:30 ` Ramkumar Ramachandra
2014-02-14 17:29 ` Jeff King
2014-02-14 18:56 ` 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=xmqqk3cyk4oz.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
--cc=tr@thomasrast.ch \
/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.