From: Kaartic Sivaraam <kaartic.sivaraam@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: Sun, 30 May 2021 23:00:10 +0530 [thread overview]
Message-ID: <4d51b7bf-966c-c3fc-ce1a-62c0db4af29a@gmail.com> (raw)
In-Reply-To: <B932C097-1B91-4D59-9CC7-1B91C86FA1A1@gmail.com>
Hi Atharva,
On 30/05/21 12:37 pm, 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
>
Nice post!
Just one suggestion. While reading, I felt that it would've been
nice if it had a few links. For instance,
> The patch that I ended up sending this week is heavily based on
> the work of two generations of GSoC programmers who struggled
> over this problem.
The text above could've had a link somewhere to the patch you sent
to the mailing list:
https://public-inbox.org/git/20210528081224.69163-1-raykar.ath@gmail.com/
> I studied Shourya’s stalled patch, parts of which had already
> been reviewed.
... and the above text could've had a link to Shourya's patch
series you mention:
https://public-inbox.org/git/20201214231939.644175-1-periperidip@gmail.com/
> In the spirit of Git being “the stupid content tracker”, I have
> decided to actually live up to that phrase and keep a track of
> my stupid moments in this section of my weekly reports, in the
> hopes that there is something here to learn from.
Good initiative. It indeed might turn out to be very helpful.
I won't surprised if it even turns out to help you, sometime in the
future ;-)
> For whatever reason, I thought of the most convoluted explanations,
> not realising that they actually don’t make any sense. Thoughts like:
> “Is the memory buffer not having tab separated tokens? Are they
> separated by some special whitespace character??”
I could totally feel you here. Things would get better over time.
Hope this helps,
Sivaraam
next prev parent reply other threads:[~2021-05-30 17:30 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 [this message]
2021-05-31 5:41 ` Atharva Raykar
2021-05-31 6:55 ` Bagas Sanjaya
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
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=4d51b7bf-966c-c3fc-ce1a-62c0db4af29a@gmail.com \
--to=kaartic.sivaraam@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.
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).