public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Mahi Kassa <mahlet.takassa@gmail.com>
To: git@vger.kernel.org
Cc: karthik.188@gmail.com, jltobler@gmail.com
Subject: [GSoC] Proposal direction for improving the new git repo command
Date: Tue, 24 Mar 2026 20:06:22 +0100	[thread overview]
Message-ID: <20260324190622.309591-1-mahlet.takassa@gmail.com> (raw)

Hello,

I am preparing a GSoC 2026 application for Git and would like to ask for feedback on the project direction I am currently exploring.

The idea I am focusing on is "Improve the new git repo command". My current plan is to work on incremental improvements to "git repo info" and "git repo structure", with an emphasis on changes that are useful, reviewable and consistent with existing Git command behavior.

In particular, I am currently considering:
  - adding useful repository information to "git repo info" that users currently need other commands to look up
  - improving "git repo structure" with additional or better-organized repository statistics
  - keeping the work split into small patches, with tests and documentation updates as needed

I have been reading through "builtin/repo.c" and the related tests while working on my microproject, and I recently sent a small patch related to "git repo" help behavior as part of my application preparation.

I would appreciate feedback on whether this seems like a reasonable direction, and especially on:
  - which "git repo info" improvements would be most valuable
  - how far "git repo structure" should go before becoming too broad
  - what scope would be realistic for a GSoC project here

Thanks,
Mahi Kassa
mahlet.takassa@gmail.com

                 reply	other threads:[~2026-03-24 19:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260324190622.309591-1-mahlet.takassa@gmail.com \
    --to=mahlet.takassa@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jltobler@gmail.com \
    --cc=karthik.188@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