From: Lucas Seiki Oshiro <lucasseikioshiro@gmail•com>
To: Christian Couder <christian.couder@gmail•com>
Cc: Kaartic Sivaraam <kaartic.sivaraam@gmail•com>,
git <git@vger•kernel.org>, karthik nayak <karthik.188@gmail•com>,
Patrick Steinhardt <ps@pks•im>, Taylor Blau <me@ttaylorr•com>,
Junio C Hamano <gitster@pobox•com>,
Siddharth Asthana <siddharthasthana31@gmail•com>,
Justin Tobler <jltobler@gmail•com>,
Ayush Chandekar <ayu.chandekar@gmail•com>,
Meet Soni <meetsoni3017@gmail•com>,
Bello Olamide <belkid98@gmail•com>,
Usman Akinyemi <usmanakinyemi202@gmail•com>,
Chandra Pratap <chandrapratap3519@gmail•com>,
Eric Ju <eric.peijian@gmail•com>
Subject: Re: Git project and GSoC 2026
Date: Thu, 29 Jan 2026 17:41:19 -0300 [thread overview]
Message-ID: <21D9FA76-F382-483E-817F-C3947C939D16@gmail.com> (raw)
In-Reply-To: <CAP8UFD29LtG2dRRB4f6mZAHNGqDmDxUV4ULYw3w3OYg15ZBBYg@mail.gmail.com>
> 6) Improve `git repo info` so it can show more information than now.
From my side, I have these features in my local backlog:
- remove the dependency on `the_repository`
- use the category as key
- add the path-related values (copied from git-rev-parse "Options for
Files"):
- git-dir
- common-dir
- toplevel
- superproject-working-tree
- add more values currently obtained through
`git rev-parse --git-path`:
- grafts file
- index file
- objects directory
- hooks directory
- git-prefix
- other paths that are adjusted by update_common_dir()
I already started to add those path-related values [1], but I think
that the major problem is deciding whether we should use relative or
absolute paths.
I also think that we have room for other information that we retrieve
through commands other than git-rev-parse.
> 7) Improve `git repo structure` so it can show more stats than now.
I don't know Justin's future plans for this command, but the idea
was to bring some functionality from git-sizer [2] to Git.
> I would be willing to mentor any of them, but I don't have much
> knowledge on `git repo`, so I think it makes more sense for me to
> avoid 6) and 7).
If you want, I can share with you some information about
git-repo-info.
I really appreciate initiatives like git-repo-structure and
git-history that bring features from other tools that make Git
easier to use. This week, I was talked independently with two
friends about how git-blame can be misleading sometimes since it
only shows the last change in a line. One of them really likes
`git log -S` for "blaming" strings and thinks that it's a too
powerful feature that is hidden inside git-log. The other one
showed me Cregit [3], a tool for blaming based on tokens
instead of lines. A "string blame" or a "token blame" could be
a nice GSoC project (but maybe for future editions).
[1] https://github.com/lucasoshiro/git/compare/master...repo-info-path/
[2] https://github.com/github/git-sizer
[3] https://github.com/cregit/cregit
next prev parent reply other threads:[~2026-01-29 20:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 11:06 Git project and GSoC 2026 Christian Couder
2026-01-19 0:44 ` Lucas Seiki Oshiro
2026-01-19 8:34 ` Christian Couder
[not found] ` <CAE7as+ZX8n4b5GypTACNCd9dWzNZTVf7fmH+5wfmEvDwEUXX6A@mail.gmail.com>
2026-01-21 14:41 ` Christian Couder
2026-01-22 5:08 ` Kaartic Sivaraam
2026-01-22 7:33 ` Christian Couder
2026-01-28 20:28 ` Kaartic Sivaraam
2026-01-29 10:20 ` Christian Couder
2026-01-29 20:41 ` Lucas Seiki Oshiro [this message]
2026-02-03 9:37 ` Christian Couder
2026-02-03 10:08 ` Christian Couder
2026-02-03 10:22 ` Christian Couder
2026-01-30 9:32 ` Karthik Nayak
2026-02-03 9:46 ` Christian Couder
2026-01-22 14:43 ` Chandra Pratap
2026-02-03 10:32 ` Christian Couder
2026-02-03 14:15 ` Chandra Pratap
2026-02-03 19:30 ` Christian Couder
2026-02-22 18:40 ` Kaartic Sivaraam
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=21D9FA76-F382-483E-817F-C3947C939D16@gmail.com \
--to=lucasseikioshiro@gmail$(echo .)com \
--cc=ayu.chandekar@gmail$(echo .)com \
--cc=belkid98@gmail$(echo .)com \
--cc=chandrapratap3519@gmail$(echo .)com \
--cc=christian.couder@gmail$(echo .)com \
--cc=eric.peijian@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=jltobler@gmail$(echo .)com \
--cc=kaartic.sivaraam@gmail$(echo .)com \
--cc=karthik.188@gmail$(echo .)com \
--cc=me@ttaylorr$(echo .)com \
--cc=meetsoni3017@gmail$(echo .)com \
--cc=ps@pks$(echo .)im \
--cc=siddharthasthana31@gmail$(echo .)com \
--cc=usmanakinyemi202@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