From: Kousik Sanagavarapu <five231003@gmail.com>
To: git@vger.kernel.org
Cc: Christian Couder <christian.couder@gmail.com>,
Hairom Verma <hariom18599@gmail.com>
Subject: Re: [GSoC] Blog
Date: Thu, 3 Aug 2023 01:22:20 +0530 [thread overview]
Message-ID: <ZMqz9D7Y6-9-UU5V@five231003> (raw)
In-Reply-To: <ZIdrQybUsjEcxMrb@five231003>
Hi,
Week 10 blog is here
Week 10: https://five-sh.github.io/2023/08/02/week10
Feel free to suggest any changes or comment on or off list.
Thanks
next prev parent reply other threads:[~2023-08-02 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 19:00 [GSoC] Blog Kousik Sanagavarapu
2023-06-14 19:50 ` Kousik Sanagavarapu
2023-06-21 18:19 ` Kousik Sanagavarapu
2023-06-28 20:01 ` Kousik Sanagavarapu
2023-07-05 20:01 ` Kousik Sanagavarapu
2023-07-12 19:43 ` Kousik Sanagavarapu
2023-07-20 20:57 ` Kousik Sanagavarapu
2023-07-26 20:38 ` Kousik Sanagavarapu
2023-08-02 19:52 ` Kousik Sanagavarapu [this message]
2023-08-09 19:29 ` Kousik Sanagavarapu
2023-08-16 20:24 ` Kousik Sanagavarapu
2023-08-26 19:34 ` Kousik Sanagavarapu
-- strict thread matches above, loose matches on Subject: below --
2023-06-19 14:53 Shuqi Liang
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=ZMqz9D7Y6-9-UU5V@five231003 \
--to=five231003@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@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 read-only IMAP folder(s) and NNTP newsgroup(s).