From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ab/bug-if-bug (was: What's cooking in git.git (Jun 2022, #01; Wed, 1))
Date: Thu, 02 Jun 2022 16:46:52 +0200 [thread overview]
Message-ID: <220602.861qw7yvep.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqee07q3xc.fsf@gitster.g>
On Wed, Jun 01 2022, Junio C Hamano wrote:
> * ab/bug-if-bug (2022-06-01) 6 commits
> - cache-tree.c: use bug() and BUG_if_bug()
> - receive-pack: use bug() and BUG_if_bug()
> - parse-options.c: use optbug() instead of BUG() "opts" check
> - parse-options.c: use new bug() API for optbug()
> - usage.c: add a non-fatal bug() function to go with BUG()
> - common-main.c: move non-trace2 exit() behavior out of trace2.c
>
> A new bug() and BUG_if_bug() API is introduced to make it easier to
> uniformly log "detect multiple bugs and abort in the end" pattern.
>
> Will merge to 'next'?
> source: <cover-v2-0.6-00000000000-20220531T164806Z-avarab@gmail.com>
I think it should be ready with a hopefully final re-roll at
https://lore.kernel.org/git/cover-v3-0.6-00000000000-20220602T122106Z-avarab@gmail.com/
addressing the outstanding v2 comments. Thanks!
next prev parent reply other threads:[~2022-06-02 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 0:55 What's cooking in git.git (Jun 2022, #01; Wed, 1) Junio C Hamano
2022-06-02 1:16 ` gc/zero-length-branch-config-fix (was Re: What's cooking in git.git (Jun 2022, #01; Wed, 1)) Glen Choo
2022-06-02 8:37 ` Ævar Arnfjörð Bjarmason
2022-06-02 12:13 ` ab/env-array (was: " Ævar Arnfjörð Bjarmason
2022-06-02 12:25 ` What's cooking in git.git (Jun 2022, #01; Wed, 1) Derrick Stolee
2022-06-02 14:07 ` Jeff Hostetler
2022-06-02 14:46 ` Ævar Arnfjörð Bjarmason [this message]
2022-06-02 14:47 ` ab/hooks-regression-fix (was: What's cooking in git.git (Jun 2022, #01; Wed, 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
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=220602.861qw7yvep.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.
Code repositories for project(s) associated with this public 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).