All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Justin Tobler <jltobler@gmail.com>,  git@vger.kernel.org
Subject: Re: [PATCH 2/2] object-file: return error on index-pack abnormal exit
Date: Tue, 10 Nov 2026 08:43:17 -0800	[thread overview]
Message-ID: <xmqqmrrgtz6i.fsf@gitster.g> (raw)
In-Reply-To: <4c7c44df-4eca-4abf-a825-1bb3b16015c2@gmail.com> (Kaartic Sivaraam's message of "Tue, 10 Nov 2026 14:34:02 +0530")

Kaartic Sivaraam <kaartic.sivaraam@gmail.com> writes:

>> Personally, I somehow find that the original "unless we positively
>> declare success, default to 'ret = -1', and if we may have detected
>> more specific error, return it back, and reset ret to 0 when we see
>> a success" easier to follow, but that may be subjective preference.
>
> +1. I too have a slight preference for the old flow of having ret = -1 
> and resetting it when there's no error. It may not be worth a re-roll, 
> though.

Note that my comment you quoted was made with a misunderstanding
of the patch and misses one important point, which is that
read_index_pack_report() used to overwrite "ret" even when it
succeeded, but the new code uses a separate variable to avoid
clobbering "ret" when the call succeeds.

In other words, the original failed to honor the "have ret = -1
and reset to 0 only after seeing everything go well" pattern,
either, and Justin's patch is a definite improvement.

  reply	other threads:[~2026-11-10 16:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 21:24 [PATCH 0/2] object-file: small error handling follow-ups Justin Tobler
2026-11-03 21:24 ` [PATCH 1/2] object-file: warn on failed unlink Justin Tobler
2026-11-04 23:00   ` Junio C Hamano
2026-11-03 21:24 ` [PATCH 2/2] object-file: return error on index-pack abnormal exit Justin Tobler
2026-11-04 23:06   ` Junio C Hamano
2026-11-05 18:09     ` Justin Tobler
2026-11-10  9:04     ` Kaartic Sivaraam
2026-11-10 16:43       ` Junio C Hamano [this message]
2026-11-10 17:57         ` Kaartic Sivaraam
2026-11-10 19:25           ` Justin Tobler
2026-11-05 15:30   ` Patrick Steinhardt
2026-11-05 18:06     ` Justin Tobler
2026-11-04 13:37 ` [PATCH 0/2] object-file: small error handling follow-ups Karthik Nayak

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=xmqqmrrgtz6i.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jltobler@gmail.com \
    --cc=kaartic.sivaraam@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.