From: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
To: git <git@vger.kernel.org>
Cc: Karthik Nayak <karthik.188@gmail.com>, Patrick Steinhardt <ps@pks.im>
Subject: [GSoC] Blog: Machine-Readable Repository Information Query Tool (week 3)
Date: Thu, 26 Jun 2025 21:26:27 -0300 [thread overview]
Message-ID: <01D987DF-4B04-4DCE-BDD7-48E1492DF12F@gmail.com> (raw)
In-Reply-To: <A203C3BB-AEC9-457E-87B8-189B81C579BF@gmail.com>
Hi!
I forgot to send here before, but I updated my GSoC blog with the third week!
You can check it here:
https://lucasoshiro.github.io/gsoc-en/#week-3-jun-16th-to-jun-22th
next prev parent reply other threads:[~2025-06-27 0:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 20:53 [GSoC] Blog: Machine-Readable Repository Information Query Tool Lucas Seiki Oshiro
2025-06-12 22:55 ` Ben Knoble
2025-06-15 21:29 ` Lucas Seiki Oshiro
2025-06-18 19:31 ` Lucas Seiki Oshiro
2025-06-27 0:26 ` Lucas Seiki Oshiro [this message]
2025-07-02 20:35 ` [GSoC] Blog: Machine-Readable Repository Information Query Tool (week 4) Lucas Seiki Oshiro
2025-07-08 20:27 ` [GSoC] Blog: Machine-Readable Repository Information Query Tool (week 5) Lucas Seiki Oshiro
2025-07-15 0:34 ` [GSoC] Blog: Machine-Readable Repository Information Query Tool (week 6) Lucas Seiki Oshiro
2025-07-22 0:49 ` [GSoC] Blog: Machine-Readable Repository Information Query Tool (week 7) Lucas Seiki Oshiro
2025-07-29 15:01 ` [GSoC] Blog: Machine-Readable Repository Information Query Tool (week 8) Lucas Seiki Oshiro
2025-08-05 19:05 ` [GSoC] Blog: Machine-Readable Repository Information Query Tool (week 9) Lucas Seiki Oshiro
2025-08-21 13:00 ` [GSoC] Blog: Machine-Readable Repository Information Query Tool (week 11) Lucas Seiki Oshiro
2025-08-26 20:20 ` [GSoC] Blog: Machine-Readable Repository Information Query Tool (week 12) Lucas Seiki Oshiro
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=01D987DF-4B04-4DCE-BDD7-48E1492DF12F@gmail.com \
--to=lucasseikioshiro@gmail.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=ps@pks.im \
/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).