From: Atharva Raykar <raykar.ath@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [GSoC] My Git Dev Blog
Date: Mon, 31 May 2021 11:11:29 +0530 [thread overview]
Message-ID: <374870FA-CAAA-4027-9AD6-E08EF63D85CD@gmail.com> (raw)
In-Reply-To: <4d51b7bf-966c-c3fc-ce1a-62c0db4af29a@gmail.com>
On 30-May-2021, at 23:00, Kaartic Sivaraam <kaartic.sivaraam@gmail.com> wrote:
>
> Hi Atharva,
>
> [...]
>
> 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/
Sure. Thanks for saving me some of the effort to get the links :D
next prev parent reply other threads:[~2021-05-31 5:41 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=374870FA-CAAA-4027-9AD6-E08EF63D85CD@gmail.com \
--to=raykar.ath@gmail.com \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.