Re: [PATCH] replace-refs: fix support of qualified replace ref paths

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 30, 2025, 00:11 UTC
Message-ID: <xmqqselq33v6.fsf@gitster.g>
In-Reply-To: <CAPMMpohgEXVPHKCQtvc-zLC35qtY+qJ9WgQO_quOgUG01eyTOw@mail.gmail.com>

Tao Klerks <tao@klerks.biz> writes:

> This is already accounted for with a hard error: If you end up with
> duplicate replace ref targets, many operations fail with a clear
> error. Clean up your replace refs and you're off to the races again.

OK. As long as that safety is there, I offhand see no more reason to forbid it. As you said, it can lead to a useful use case.