From: Paul-Sebastian Ungureanu <ungureanupaulsebastian@gmail.com>
To: Alban Gruin <alban.gruin@gmail.com>, Git List <git@vger.kernel.org>
Cc: Stefan Beller <sbeller@google.com>,
Pratik Karki <predatoramigo@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [GSoC] GSoC with git, week 11
Date: Wed, 18 Jul 2018 00:55:47 +0300 [thread overview]
Message-ID: <b33c711f-ec95-76cc-73e8-9a421e4d1a7f@gmail.com> (raw)
In-Reply-To: <866fb524-6fef-ca6c-da79-b63405b5e578@gmail.com>
Hello,
On 17.07.2018 21:41, Alban Gruin wrote:
> Hi,
>
> I published a new blog post about last week:
>
> https://blog.pa1ch.fr/posts/2018/07/17/en/gsoc2018-week11.html
>
> Cheers,
> Alban
>
Great entry!
Here I am too, with two updates on the blog:
* The weekly blog.
https://ungps.github.io/2018/07/15/week-11/
* Some of my thoughts on GSoC.
https://ungps.github.io/2018/07/16/About-GSoC/
Best,
Paul
prev parent reply other threads:[~2018-07-17 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 18:41 [GSoC] GSoC with git, week 11 Alban Gruin
2018-07-17 21:55 ` Paul-Sebastian Ungureanu [this message]
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=b33c711f-ec95-76cc-73e8-9a421e4d1a7f@gmail.com \
--to=ungureanupaulsebastian@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=alban.gruin@gmail.com \
--cc=git@vger.kernel.org \
--cc=predatoramigo@gmail.com \
--cc=sbeller@google.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.
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 NNTP newsgroup(s).