From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Han-Wen Nienhuys <hanwen@google.com>
Subject: ab/refs-errno-cleanup
Date: Fri, 01 Oct 2021 16:48:56 +0200 [thread overview]
Message-ID: <87ee94rdq7.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqh7e18soj.fsf@gitster.g>
On Thu, Sep 30 2021, Junio C Hamano wrote:
> * ab/refs-errno-cleanup (2021-08-25) 4 commits
> - refs: make errno output explicit for refs_resolve_ref_unsafe
> - refs: explicitly return failure_errno from parse_loose_ref_contents
> - branch tests: test for errno propagating on failing read
> - refs: add failure_errno to refs_read_raw_ref() signature
> (this branch uses ab/refs-files-cleanup and hn/refs-errno-cleanup.)
>
> The "remainder" of hn/refs-errno-cleanup topic.
>
> What's the status of this one? Meh?
I'v got two topics that have been waiting on ab/refs-files-cleanup &
hn/refs-errno-cleanup graduating:
A. Post-ab/refs-files-cleanup: cleanup builtin/reflog.c for the state of
the new API, I did a bare minimum of fixes there in
ab/refs-files-cleanup, but the end-state doesn't make much sense if
you aren't considering the history of now-gone OID locking "features".
B. Post-ab/refs-errno-cleanup: Reach the end-state of no refs.c APIs
relying on, or pretending to rely on "errno" being returned
upwards. This was previously submitted as[1], but the topic was since
slimmed down into the current ab/refs-errno-cleanup.
The "B" needs this ab/refs-errno-cleanup. I think (and I think Han-Wen
would agree) that it leaves the refs API in a much better state for
reftable integration.
1. https://lore.kernel.org/git/cover-00.17-00000000000-20210711T162803Z-avarab@gmail.com/
next prev parent reply other threads:[~2021-10-01 15:01 UTC|newest]
Thread overview: 16+ 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 ` What's cooking in git.git (Sep 2021, #09; Thu, 30) Ævar Arnfjörð Bjarmason
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 ` Ævar Arnfjörð Bjarmason [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2021-10-04 23:44 What's cooking in git.git (Oct 2021, #01; Mon, 4) Junio C Hamano
2021-10-05 16:01 ` ab/refs-errno-cleanup Æ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=87ee94rdq7.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hanwen@google.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).