mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Andrew Ardill <>
To: Johannes Schindelin <>
Cc: Pratik Karki <>, git <>,
	Christian Couder <>,
	Stefan Beller <>
Subject: Re: [GSoC] Info: new blog series of my work on Git GSoC '18
Date: Thu, 3 May 2018 10:46:44 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2 May 2018 at 17:12, Johannes Schindelin <> wrote:
> Hi Pratik,
> On Wed, 2 May 2018, Pratik Karki wrote:
>> As promised in my proposal, I've started
>> to write a blog series of GSoC '18 with Git. The initial blog is up.
>> You can find it here[1]. The initial one is just to get started and
>> from next iterations, I'll start detailing of my work towards converting
>> rebase to builtin.
>> [1]:
> This is awesome! Thanks for doing this,
> Dscho

Agreed, was fun to read.

I'd encourage you to post to the list when you blog, or perhaps
include a link to the blog as part of any regular updates you give on
your project progress.

Would also make for an interesting addition to the newsletter.

I know it can be difficult to sit down and write about what you're
doing, especially when it feels like you could be focusing on 'real
work'. Hopefully you will find the process rewarding; I'm looking
forward to reading about what you find easy and hard, how you learn
the git developer processes, and the challenges you find in converting
shell scripts to a built-in. I'm sure other people are too, and I'll
bet the ones who have been there before will have feedback for you as

I'd find it interesting even if it was a 5-line bullet list of what's
going through your mind with respect to the project! Looking forward
to following along.


Andrew Ardill

  reply	other threads:[~2018-05-03  0:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02  3:39 [GSoC] Info: new blog series of my work on Git GSoC '18 Pratik Karki
2018-05-02  7:12 ` Johannes Schindelin
2018-05-03  0:46   ` Andrew Ardill [this message]
2018-05-03  1:49     ` Pratik Karki

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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

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).