Re: scratch/igc as a feature branch [was: Re: igc: trying to chase a crash]

[Andrea Corallo <acorallo@gnu.org>]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andrea Corallo <acorallo@gnu.org>
>> Cc: chad <yandros@gmail.com>,  Óscar Fuentes <ofv@wanadoo.es>,
>>  emacs-devel@gnu.org,  Pip Cet <pipcet@protonmail.com>
>> Date: Wed, 27 Nov 2024 05:18:08 -0500
>> 
>> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>> 
>> >> Absolutely, still I think few things are probably really low cost (the
>> >> feature branch comes to my mind).
>> >>
>> >
>> > Maintainers could just decide to do it, cough, cough :-).
>> 
>> Maintainers could decide autonomously, but IMO is more about developers
>> of that branch being okay with the decision.  The implications are,
>> other than the name change, not being able to force push.
>> 
>> That said not only I'm okay with having scratch/icg being pushed as
>> feature/icg, but I long time suggested that :)
>
> The question is indeed what kind of trouble this could cause.  If it
> loses the history, I wouldn't do it, since the fact that it's under
> scratch/ is not a catastrophe, IMO.

Sure, my idea would be to just push the current head of scratch/icg to
feature/igc (and remove the first), so no history would be lost.

  Andrea