From: Kaartic Sivaraam Date: Sun, 30 May 2021 17:30:10 GMT Subject: Re: [GSoC] My Git Dev Blog Message-ID: <4d51b7bf-966c-c3fc-ce1a-62c0db4af29a@gmail.com> In-Reply-To: Hi Atharva, On 30/05/21 12:37 pm, Atharva Raykar wrote: > Hi, > > On 22-May-2021, at 22:12, Atharva Raykar 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