From: Justin Tobler <jltobler@gmail.com>
To: K Jayatheerth <jayatheerthkulkarni2005@gmail.com>
Cc: GIT Mailing-list <git@vger.kernel.org>,
Patrick Steinhardt <ps@pks.im>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [Question] Ascii histograms for repo structure
Date: Mon, 16 Mar 2026 07:46:18 -0500 [thread overview]
Message-ID: <abf6l15w1MNXIzo8@denethor> (raw)
In-Reply-To: <CA+rGoLd0_gc36EBv_DieVqtjLn1FL39vtT5ib1fEbk-+OvPP6A@mail.gmail.com>
On 26/03/16 02:56PM, K Jayatheerth wrote:
> Hi Justin,
>
> I was catching up on the recent patch series
> builtin/repo: include largest object information
> _cc'ing everyone in the discussion_
>
> The discussion with Patrick and Junio about
> adding object size and entry distributions (histograms)
> to the git repo structure output was interesting to me.
>
> I noticed you mentioned planning to explore this in a follow-up series.
> I am currently finalizing my GSoC 2026 proposal to improve the git repo command,
> and I wanted to include implementing these streaming buckets
> and ASCII bar charts as one of my core project goals.
>
> Before I officially commit to it in my proposal,
> I wanted to check in and see if you have already started working on
> this locally,
> or if you would be open to me picking it up as part of my GSoC
> project? I certainly
> don't want to step on your toes or duplicate any effort if you already
> have patches in flight.
I don't have anything started at the moment and would certainly be ok
with someone else picking up the topic. Thanks for taking an interest! :)
Thanks,
-Justin
prev parent reply other threads:[~2026-03-16 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 9:26 [Question] Ascii histograms for repo structure K Jayatheerth
2026-03-16 12:46 ` Justin Tobler [this message]
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=abf6l15w1MNXIzo8@denethor \
--to=jltobler@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jayatheerthkulkarni2005@gmail.com \
--cc=ps@pks.im \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.