From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Atharva Raykar <raykar.ath@gmail.com>, git <git@vger.kernel.org>
Cc: Christian Couder <christian.couder@gmail.com>,
Shourya Shukla <shouryashukla.oo@gmail.com>
Subject: Re: [GSoC] My Git Dev Blog
Date: Mon, 31 May 2021 13:55:53 +0700 [thread overview]
Message-ID: <2691ddbb-940d-34e2-6865-85890a96ec90@gmail.com> (raw)
In-Reply-To: <B932C097-1B91-4D59-9CC7-1B91C86FA1A1@gmail.com>
Hi Atharva,
On 30/05/21 14.07, Atharva Raykar wrote:
> Hi,
>
> On 22-May-2021, at 22:12, Atharva Raykar <raykar.ath@gmail.com> wrote:
>>
>> [...]
>> I will update this thread every week when I make a new post.
>
> A new blog post is out at: http://atharvaraykar.me/gitnotes/week2
>
> Summary of what's in it:
>
> * Deliberate and not-so-deliberate things left behind by developers
> -- and why they are valuable (especially for my first patch)
>
> * My work as putting cherries on top of other people's cakes
>
> * A debugging blooper -- showing my mistakes in the hopes that
> there is something to learn from it
>
> The usual things apply: feedback and discussion is welcome.
>
I think it's better to post link to each blogpost as separate threads,
because we can discuss each posts at its own merit.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-05-31 6:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 16:42 [GSoC] My Git Dev Blog Atharva Raykar
2021-05-22 19:39 ` Philippe Blain
2021-05-23 11:50 ` Atharva Raykar
2021-05-23 8:10 ` Bagas Sanjaya
2021-05-23 11:50 ` Atharva Raykar
2021-05-30 16:41 ` Felipe Contreras
2021-05-24 20:18 ` Christian Couder
2021-05-30 7:07 ` Atharva Raykar
2021-05-30 17:30 ` Kaartic Sivaraam
2021-05-31 5:41 ` Atharva Raykar
2021-05-31 6:55 ` Bagas Sanjaya [this message]
2021-05-31 7:43 ` Atharva Raykar
2021-05-31 8:32 ` Christian Couder
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=2691ddbb-940d-34e2-6865-85890a96ec90@gmail.com \
--to=bagasdotme@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=raykar.ath@gmail.com \
--cc=shouryashukla.oo@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.
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).