From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2021, #09; Thu, 30)
Date: Fri, 01 Oct 2021 14:05:20 +0200 [thread overview]
Message-ID: <8735plrlql.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqh7e18soj.fsf@gitster.g>
On Thu, Sep 30 2021, Junio C Hamano wrote:
[I figure for this topic update of mine I'll do the split E-Mails as
dicussed in last What's Cooking, also maybe my relatively long updates
to past ones have discouraged reading...]
> * ab/designated-initializers-more (2021-09-27) 6 commits
> - builtin/remote.c: add and use SHOW_INFO_INIT
> - builtin/remote.c: add and use a REF_STATES_INIT
> - urlmatch.[ch]: add and use URLMATCH_CONFIG_INIT
> - builtin/blame.c: refactor commit_info_init() to COMMIT_INFO_INIT macro
> - daemon.c: refactor hostinfo_init() to HOSTINFO_INIT macro
> - Merge branch 'ab/designated-initializers' into ab/designated-initializers-more
> (this branch uses ab/designated-initializers.)
>
> Code clean-up.
>
> What's the status of this one? Meh?
I just re-rolled this as
https://lore.kernel.org/git/cover-v3-0.6-00000000000-20211001T102056Z-avarab@gmail.com/
As noted there I've got meaningful leak fixes that in some cases
semi-depend on this, but I did more conversions than strictly needed for
immediate follow-up I have. I'd prefer to just got this particular churn
over with if there's more memset()->*_INIT migrations needed.
So it would be great if that would be a s/Meh/grudging acceptance for
'next'/. I promise I'm taking it somewhere worthwhile :)
next prev parent reply other threads:[~2021-10-01 12:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 1:01 What's cooking in git.git (Sep 2021, #09; Thu, 30) Junio C Hamano
2021-10-01 6:20 ` en/removing-untracked-fixes [Was: Re: What's cooking in git.git (Sep 2021, #09; Thu, 30)] Elijah Newren
2021-10-01 8:51 ` Ævar Arnfjörð Bjarmason
2021-10-01 17:05 ` en/removing-untracked-fixes [ Junio C Hamano
2021-10-01 6:31 ` en/remerge-diff [Was: Re: What's cooking in git.git (Sep 2021, #09; Thu, 30)] Elijah Newren
2021-10-01 7:01 ` Jeff King
2021-10-01 12:05 ` Ævar Arnfjörð Bjarmason [this message]
2021-10-01 12:08 ` ab/fsck-unexpected-type Ævar Arnfjörð Bjarmason
2021-10-01 14:32 ` ab/parse-options-cleanup Ævar Arnfjörð Bjarmason
2021-10-01 14:35 ` ab/sanitize-leak-ci & more leak fixes soon-or-not Ævar Arnfjörð Bjarmason
2021-10-01 14:48 ` ab/refs-errno-cleanup Ævar Arnfjörð Bjarmason
2021-10-01 14:56 ` What's cooking in git.git (Sep 2021, #09; Thu, 30) Jeff Hostetler
2021-10-01 15:01 ` ab/align-parse-options-help & ab/help-config-vars Ævar Arnfjörð Bjarmason
2021-10-01 15:05 ` ab/lib-subtest Ævar Arnfjörð Bjarmason
2021-10-01 15:07 ` ab/config-based-hooks-1 Ævar Arnfjörð Bjarmason
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=8735plrlql.fsf@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).