All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: js/scalar-diagnose, was Re: What's cooking in git.git (Feb 2022, #08; Mon, 28)
Date: Tue, 01 Mar 2022 23:05:32 -0800	[thread overview]
Message-ID: <xmqqfso0omv7.fsf@gitster.g> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2203012353090.11118@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Tue, 1 Mar 2022 23:55:18 +0100 (CET)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> On Tue, 1 Mar 2022, Junio C Hamano wrote:
>
>> * js/scalar-diagnose (2022-02-06) 6 commits
>>  - scalar: teach `diagnose` to gather loose objects information
>>  - scalar: teach `diagnose` to gather packfile info
>>  - scalar diagnose: include disk space information
>>  - scalar: add `diagnose`
>>  - scalar: validate the optional enlistment argument
>>  - archive: optionally add "virtual" files
>>
>>  Implementation of "scalar diagnose" subcommand.
>>
>>  Expecting a reroll.
>>  cf. What is the status of this thing?
>>  source: <pull.1128.v2.git.1644187146.gitgitgadget@gmail.com>
>
> The status is that I'm woefully short on time and did not even manage to
> read the sub-thread between you and René (which might need another
> adjustment to the code).

FWIW, I think the subthread was mostly about "now we have a new
feature in 'git archive', do we want to use it elsewhere?" tangent
and the outcome of the discussion there won't affect this topic---as
long as this topic needs the new feature it adds to 'git archive',
and the new feature is adequately done, I do not think there is any
need for it to be redone.

Other parts of the series may or may not need reworking, but I do
not recall the details of the topic.

> So maybe set it to `On Hold` for now?

OK.

  reply	other threads:[~2022-03-02  7:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 13:42 What's cooking in git.git (Feb 2022, #08; Mon, 28) Junio C Hamano
2022-03-01 14:26 ` ds/commit-graph-gen-v2-fixes (was Re: What's cooking in git.git (Feb 2022, #08; Mon, 28)) Derrick Stolee
2022-03-01 14:58   ` Patrick Steinhardt
2022-03-01 18:07   ` Junio C Hamano
2022-03-01 22:55 ` js/scalar-diagnose, was Re: What's cooking in git.git (Feb 2022, #08; Mon, 28) Johannes Schindelin
2022-03-02  7:05   ` Junio C Hamano [this message]
2022-03-02  1:26 ` en/merge-tree (Was: Re: What's cooking in git.git (Feb 2022, #08; Mon, 28)) Elijah Newren
2022-03-07 16:31   ` Johannes Schindelin
2022-03-08  8:30     ` Elijah Newren
2022-03-09 11:46       ` Johannes Schindelin
2022-03-03 16:11 ` ab/object-file-api-updates (was: " Ævar Arnfjörð Bjarmason
2022-03-03 22:23   ` ab/object-file-api-updates Junio C Hamano

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=xmqqfso0omv7.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /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.