From: Duy Nguyen <pclouds@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git <git@vger.kernel.org>,
"Pranit Bauva" <pranit.bauva@gmail.com>,
"Lars Schneider" <larsxschneider@gmail.com>,
"Christian Couder" <christian.couder@gmail.com>,
"Jeff King" <peff@peff.net>, "Carlos Martín Nieto" <cmn@dwim.me>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Thomas Gummerer" <t.gummerer@gmail.com>
Subject: Re: GSoC 2017: application open, deadline = February 9, 2017
Date: Sat, 18 Mar 2017 16:01:50 +0700 [thread overview]
Message-ID: <CACsJy8D+VKGEtq6yMe+ZhfxKX2peCVXGZfZFckkZF_L=bWBqTg@mail.gmail.com> (raw)
In-Reply-To: <vpq1svtstud.fsf@anie.imag.fr>
On Mon, Jan 23, 2017 at 10:02 PM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> * We need to write the application, i.e. essentially polish and update
> the text here: https://git.github.io/SoC-2016-Org-Application/ and
> update the list of project ideas and microprojects :
> https://git.github.io/SoC-2017-Ideas/
> https://git.github.io/SoC-2016-Microprojects/
Probably too late for GSoc 2017, but another idea for microproject (or
microprojects) is make use of dir-iterator.h more. For recursive
directory walking, this would make the code easier to read and
potentially avoid too deep recursion. There are three or four of them,
I think.
--
Duy
next prev parent reply other threads:[~2017-03-18 10:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 15:02 GSoC 2017: application open, deadline = February 9, 2017 Matthieu Moy
2017-01-24 11:28 ` Johannes Schindelin
2017-01-24 13:32 ` Christian Couder
2017-01-25 20:45 ` Jeff King
2017-02-08 14:54 ` Matthieu Moy
2017-02-08 15:43 ` Jeff King
2017-02-09 9:42 ` Christian Couder
2017-02-09 10:15 ` Matthieu Moy
2017-02-09 10:28 ` Siddharth Kannan
2017-02-09 10:49 ` Christian Couder
2017-02-09 10:45 ` Christian Couder
2017-02-09 12:11 ` Matthieu Moy
2017-02-09 12:22 ` Matthieu Moy
2017-02-09 12:28 ` Matthieu Moy
2017-02-09 13:17 ` Christian Couder
2017-02-09 21:38 ` Johannes Schindelin
2017-02-09 21:47 ` Stefan Beller
2017-02-09 12:18 ` Pranit Bauva
2017-03-18 9:01 ` Duy Nguyen [this message]
2017-03-18 17:42 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsJy8D+VKGEtq6yMe+ZhfxKX2peCVXGZfZFckkZF_L=bWBqTg@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=christian.couder@gmail.com \
--cc=cmn@dwim.me \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
--cc=pranit.bauva@gmail.com \
--cc=t.gummerer@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).