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
