git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: git@vger.kernel.org, kristofferhaugsbakk@fastmail.com, gitster@pobox.com
Subject: Re: [PATCH v2] reflog: implement subcommand to drop reflogs
Date: Thu, 13 Mar 2025 15:45:07 +0100	[thread overview]
Message-ID: <Z9Lvc2YKr5jD5D6h@pks.im> (raw)
In-Reply-To: <CAOLa=ZQ3Rgi+yyma0Zo6uK04eu9Lk1dk_uYTU-4hFfh9POTNYA@mail.gmail.com>

On Thu, Mar 13, 2025 at 09:24:16AM -0500, Karthik Nayak wrote:
> Patrick Steinhardt <ps@pks.im> writes:
> > On Mon, Mar 10, 2025 at 01:36:25PM +0100, Karthik Nayak wrote:
> >> +			continue;
> >> +		}
> >> +
> >> +		ret |= refs_delete_reflog(get_main_ref_store(repo), ref);
> >> +		free(ref);
> >> +	}
> >
> > The code is correct, but do we want to maybe wrap this loop in the
> > `else` branch to guide the reader and make it blindingly obvious that
> > the loop does nothing `if (do_all)`?
> >
> 
> Wouldn't it be simpler to return at the end of the `if (do_all)`? I've
> added that, but if feel strongly about this form, happy to change it.

I don't feel overly strong about it. I'm not a huge fan of early
returns as I think it's easier to reason about functions if they have a
common exit path. But I can live with whatever solution you come up
with.

Patrick

  reply	other threads:[~2025-03-13 14:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 11:17 [PATCH 0/2] EDITME: cover title for 493-add-command-to-purge-reflog-entries Karthik Nayak
2025-03-07 11:17 ` [PATCH 1/2] reflog: drop usage of global variables Karthik Nayak
2025-03-07 21:19   ` Junio C Hamano
2025-03-10 11:41     ` Karthik Nayak
2025-03-10 15:24       ` Junio C Hamano
2025-03-13 13:30         ` Karthik Nayak
2025-03-07 11:17 ` [PATCH 2/2] reflog: implement subcommand to drop reflogs Karthik Nayak
2025-03-07 11:50   ` Patrick Steinhardt
2025-03-07 12:53     ` Karthik Nayak
2025-03-07 12:59       ` Patrick Steinhardt
2025-03-07 13:28         ` Karthik Nayak
2025-03-07 13:28         ` Karthik Nayak
2025-03-07 21:28     ` Junio C Hamano
2025-03-10 11:28       ` Karthik Nayak
2025-03-10  7:39 ` [PATCH 0/2] EDITME: cover title for 493-add-command-to-purge-reflog-entries Kristoffer Haugsbakk
2025-03-10 12:34   ` Karthik Nayak
2025-03-10 15:28   ` Junio C Hamano
2025-03-10 12:36 ` [PATCH v2] reflog: implement subcommand to drop reflogs Karthik Nayak
2025-03-12  7:15   ` Patrick Steinhardt
2025-03-13 14:24     ` Karthik Nayak
2025-03-13 14:45       ` Patrick Steinhardt [this message]
2025-03-14  8:40 ` [PATCH v3 0/2] " Karthik Nayak
2025-03-14  8:40   ` [PATCH v3 1/2] reflog: improve error for when reflog is not found Karthik Nayak
2025-03-14  8:40   ` [PATCH v3 2/2] reflog: implement subcommand to drop reflogs Karthik Nayak
2025-03-18 14:01     ` Christian Couder
2025-03-18 17:44       ` Junio C Hamano
2025-03-19  8:17         ` Christian Couder
2025-03-19  9:06           ` Karthik Nayak
2025-03-18 15:56     ` Toon Claes
2025-03-19  9:16       ` 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=Z9Lvc2YKr5jD5D6h@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=karthik.188@gmail.com \
    --cc=kristofferhaugsbakk@fastmail.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).