From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ab/* topics (was: What's cooking in git.git (Jun 2022, #08; Mon, 27))
Date: Mon, 27 Jun 2022 20:51:29 +0200 [thread overview]
Message-ID: <220627.86r13agcp3.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqsfnqnezx.fsf@gitster.g>
On Mon, Jun 27 2022, Junio C Hamano wrote:
> * ab/squelch-empty-fsync-traces (2022-06-23) 1 commit
> - trace2: don't include "fsync" events in all trace2 logs
>
> Omit fsync-related trace2 entries when their values are all zero.
>
> Expecting a reroll.
> cf. <xmqqh74byy19.fsf@gitster.g>
> source: <patch-1.1-df87e515efd-20220623T154943Z-avarab@gmail.com>
Will re-roll.
> * ab/test-quoting-fix (2022-06-21) 3 commits
> - config tests: fix harmless but broken "rm -r" cleanup
> - test-lib.sh: fix prepend_var() quoting issue
> - tests: add missing double quotes to included library paths
>
> Fixes for tests when the source directory has unusual characters in
> its path, e.g. whitespaces, double-quotes, etc.
>
> Expecting a reroll.
> source: <cover-0.3-00000000000-20220621T221928Z-avarab@gmail.com>
Ditto.
> * ab/submodule-cleanup (2022-06-15) 12 commits
> - git-sh-setup.sh: remove "say" function, change last users
> - git-submodule.sh: use "$quiet", not "$GIT_QUIET"
> - submodule--helper: eliminate internal "--update" option
> - submodule--helper: understand --checkout, --merge and --rebase synonyms
> - submodule--helper: report "submodule" as our name in "-h" output
> - submodule--helper: rename "absorb-git-dirs" to "absorbgitdirs"
> - submodule update: remove "-v" option
> - submodule--helper: have --require-init imply --init
> - git-submodule.sh: remove unused top-level "--branch" argument
> - git-submodule.sh: make "$cached" variable a boolean
> - git-submodule.sh: remove unused $prefix var and --super-prefix
> - git-submodule.sh: remove unused sanitize_submodule_env()
>
> Further preparation to turn git-submodule.sh into a builtin.
>
> Will merge to 'next'?
> source: <cover-v2-00.12-00000000000-20220613T220150Z-avarab@gmail.com>
I have a locally queued re-roll of this addressing Glen's comments. I
don't think there's anything broken in this as-is, but hopefully
clarifying the --super-prefix situation a bit more will help.
> * ab/test-without-templates (2022-06-06) 7 commits
> - tests: don't assume a .git/info for .git/info/sparse-checkout
> - tests: don't assume a .git/info for .git/info/exclude
> - tests: don't assume a .git/info for .git/info/refs
> - tests: don't assume a .git/info for .git/info/attributes
> - tests: don't assume a .git/info for .git/info/grafts
> - tests: don't depend on template-created .git/branches
> - t0008: don't rely on default ".git/info/exclude"
>
> Tweak tests so that they still work when the "git init" template
> did not create .git/info directory.
>
> Will merge to 'next'?
> source: <cover-v2-0.7-00000000000-20220603T110506Z-avarab@gmail.com>
Discussed in
https://lore.kernel.org/git/220627.86zghygdtd.gmgdl@evledraar.gmail.com/;
I think it's ready, but you've got some reservations.
prev parent reply other threads:[~2022-06-27 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 18:22 What's cooking in git.git (Jun 2022, #08; Mon, 27) Junio C Hamano
2022-06-27 18:51 ` Ævar Arnfjörð Bjarmason [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=220627.86r13agcp3.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).