git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSoC] Project Proposal: Machine-Readable Repository Information Query Tool

From
Patrick Steinhardt <ps@pks.im>
Date
Apr 4, 2025, 09:09 UTC
Message-ID
<Z--h3rhY5XAERVHm@pks.im>
In-Reply-To
<BC393559-6A33-447D-9AE8-BB2D9D0BC0D6@gmail.com>
On Thu, Apr 03, 2025 at 03:02:51PM -0300, Lucas Seiki Oshiro wrote:
Show 6 quoted lines
> > 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
Previous: Lucas Seiki OshiroNext: Lucas Seiki Oshiro
Message 4 of 5 in “[GSoC] Project Proposal: Machine-Readable Repository Information Query Tool”
  1. Lucas Seiki OshiroApr 2, 2025
  2. Patrick SteinhardtApr 3, 2025
  3. Lucas Seiki OshiroApr 3, 2025
  4. Patrick SteinhardtApr 4, 2025
  5. Lucas Seiki OshiroApr 4, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.