git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: js/scalar-diagnose, was Re: What's cooking in git.git (May 2022, #04; Thu, 12)
Date: Fri, 13 May 2022 14:06:56 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2205131404280.352@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqilqacmmd.fsf@gitster.g>

[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]

Hi Junio,

On Thu, 12 May 2022, Junio C Hamano wrote:

> * js/scalar-diagnose (2022-05-12) 8 commits
>  - fixup: archive: optionally add "virtual" files
>  - scalar: teach `diagnose` to gather loose objects information
>  - scalar: teach `diagnose` to gather packfile info
>  - scalar diagnose: include disk space information
>  - scalar: implement `scalar diagnose`
>  - scalar: validate the optional enlistment argument
>  - archive --add-file-with-contents: allow paths containing colons
>  - archive: optionally add "virtual" files
>
>  Implementation of "scalar diagnose" subcommand.
>
>  Will merge to 'next' after squashing the fix in?
>  source: <pull.1128.v4.git.1652210824.gitgitgadget@gmail.com>

Yes, please!

My first reaction was: but wait, what about the file mode? Then I
remembered that René offered the opinion that we could easily introduce
`--add-executable-file-with-contents` _iff_ we need that at some stage,
and when I considered symbolic links, I noticed that the `--add-file`
option does not accept those in the first place, so it would be funny if
`--add-file-with-contents` supported symbolic links.

Thanks,
Dscho

  reply	other threads:[~2022-05-13 12:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13  0:16 Junio C Hamano
2022-05-13 12:06 ` Johannes Schindelin [this message]
2022-05-13 15:34   ` js/scalar-diagnose, was " Junio C Hamano
2022-05-13 19:43 ` Jeff Hostetler

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nycvar.QRO.7.76.6.2205131404280.352@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --subject='js/scalar-diagnose, was Re: What'\''s cooking in git.git (May 2022, #04; Thu, 12)' \
    /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

Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).