Re: [PATCH v3] maintenance: add prune-remote-refs task

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 7, 2025, 18:48 UTC
Message-ID: <xmqqmsg2sbn5.fsf@gitster.g>
In-Reply-To: <CAG=Um+1tD+taKyN35x6q8ynjgrp+nVPBbuff5FUm6HUp3qe+fw@mail.gmail.com>

Shubham Kanodia <shubham.kanodia10@gmail.com> writes:

> Junio, what do you think about my previous suggestion — do you think
> that changing the remote behaviours is a blocker for this change to
> make its way to master?

Yes, changing the behaviour of an existing command in the same patch that adds a new feature, and doing so without clearly explaining why such a change is a good idea in the proposed log message, are both huge blockers. Not just to 'master', but to anywhere near 'next'.

Thanks.