From: Lucas Seiki Oshiro <lucasseikioshiro@gmail•com>
To: Patrick Steinhardt <ps@pks•im>
Cc: git@vger•kernel.org, karthik.188@gmail•com, shyamthakkar001@gmail•com
Subject: Re: [GSoC] Project Proposal: Machine-Readable Repository Information Query Tool
Date: Fri, 4 Apr 2025 12:01:18 -0300 [thread overview]
Message-ID: <A951AB6E-2CFD-4849-BF93-3DC34EC3637A@gmail.com> (raw)
In-Reply-To: <Z--h3rhY5XAERVHm@pks.im>
> So the intent of the command should be clearly defined to avoid this.
Thanks, Patrick! I'll send a more focused v2 soon.
prev parent reply other threads:[~2025-04-04 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 18:22 [GSoC] Project Proposal: Machine-Readable Repository Information Query Tool Lucas Seiki Oshiro
2025-04-03 10:14 ` Patrick Steinhardt
2025-04-03 18:02 ` Lucas Seiki Oshiro
2025-04-04 9:09 ` Patrick Steinhardt
2025-04-04 15:01 ` Lucas Seiki Oshiro [this message]
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=A951AB6E-2CFD-4849-BF93-3DC34EC3637A@gmail.com \
--to=lucasseikioshiro@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=karthik.188@gmail$(echo .)com \
--cc=ps@pks$(echo .)im \
--cc=shyamthakkar001@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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