From: Patrick Steinhardt <ps@pks.im>
To: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
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 11:09:50 +0200 [thread overview]
Message-ID: <Z--h3rhY5XAERVHm@pks.im> (raw)
In-Reply-To: <BC393559-6A33-447D-9AE8-BB2D9D0BC0D6@gmail.com>
On Thu, Apr 03, 2025 at 03:02:51PM -0300, Lucas Seiki Oshiro wrote:
> > This kind of information is exposed via git-rev-parse(1) already, see
> > the section "Options for Files".
>
> Thanks for your clarification! But still, I was discussing with people
> here at my university who deals directly with research on FLOSS
> repositories, is it worth to find other uses cases for this new command?
It doesn't hurt to think about additional usecases, sure. But one of the
things that I want to caution against is that we now create the next
"grab bag" of unrelated features under a common name. After all, we are
trying to fix exactly this state in git-rev-parse(1). So the intent of
the command should be clearly defined to avoid this.
Patrick
next prev parent reply other threads:[~2025-04-04 9:09 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 [this message]
2025-04-04 15:01 ` 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=Z--h3rhY5XAERVHm@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=lucasseikioshiro@gmail.com \
--cc=shyamthakkar001@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 NNTP newsgroup(s).