git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Pratik Karki <predatoramigo@gmail.com>
To: Stefan Beller <sbeller@google.com>
Cc: Alban Gruin <alban.gruin@gmail.com>,
	Git List <git@vger.kernel.org>,
	Paul-Sebastian Ungureanu <ungureanupaulsebastian@gmail.com>,
	Christian Couder <christian.couder@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [GSoC] Yet another blog series about the GSoC
Date: Tue, 8 May 2018 08:14:17 +0545	[thread overview]
Message-ID: <CAOZc8M934x8HWiPVmv7OkaApjNkQ-t5jw51Fv9Zg7pwCyLt_HA@mail.gmail.com> (raw)
In-Reply-To: <CAGZ79kZU-LsQqYxUeFzxk+6wpmUY0rKpWBa4Us+n9c60JE-frg@mail.gmail.com>

On Tue, May 8, 2018 at 12:20 AM, Stefan Beller <sbeller@google.com> wrote:
> Hi Pratik,
Hi Stefan,

> On Sat, May 5, 2018 at 5:24 AM, Pratik Karki <predatoramigo@gmail.com> wrote:
>> On Sat, May 5, 2018 at 5:11 PM, Alban Gruin <alban.gruin@gmail.com> wrote:
>>> Hi everybody,
>>>
>>> as my fellow students, I started a blog series about my GSoC project[1].
>>> First, I wanted to post them directly on the mailing list, but a blog
>>> allows me to edit the content easily if needed.
>>>
>>> Any feedback is welcome!
>>>
>>> [1] https://blog.pa1ch.fr/posts/2018/05/05/en/gsoc2018-week-1.html
>>>
>>> Cheers,
>>> Alban Gruin
>
> Thanks for blogging about GSoC!
>
>> Nice post. Great job, Alban.
>> Just a little typo I found out there: hazardous -> hasardous.
>
> I would think hazardous is correct, both in British as well as
> American English, I cannot speak for more.

I believe I kept the notation wrong in the mail I sent earlier.
Actually, Alban had hasardous typo. I corrected him.
I guess the notation should have been: hasardous -> hazardous.
Sorry. :-)

Cheers,
Pratik Karki

      reply	other threads:[~2018-05-08  2:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-05 11:26 [GSoC] Yet another blog series about the GSoC Alban Gruin
2018-05-05 12:24 ` Pratik Karki
2018-05-05 13:43   ` Christian Couder
2018-05-07 18:35   ` Stefan Beller
2018-05-08  2:29     ` Pratik Karki [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

  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=CAOZc8M934x8HWiPVmv7OkaApjNkQ-t5jw51Fv9Zg7pwCyLt_HA@mail.gmail.com \
    --to=predatoramigo@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=alban.gruin@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sbeller@google.com \
    --cc=ungureanupaulsebastian@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).