Re: New git-rebase backend: no way to drop already-empty commits

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 7, 2020, 21:55 UTC
Message-ID: <xmqqd08jrmeu.fsf@gitster.c.googlers.com>
In-Reply-To: <CABPp-BF8eokQTVwgo80ffq3tn=NA=mPf7oymce5P4itDyZBiMg@mail.gmail.com>

Elijah Newren <newren@gmail.com> writes:

Show 13 quoted lines

>> As we will be dropping 'apply' that could be used as an escape
>> hatch, before we do so, we should teach the other backends an
>> alternate escape hatch to help those who have been depending on the
>> behaviour of 'apply' that discards the empty ones, whether they
>> become empty, or they are empty from the beginning.  I think the
>> "has contents originally but becomes empty" side is already taken
>> care of, so we'd need to make sure it is easy to optionally discard
>> the ones that are originally empty.
>>
>> Thanks.
>
> I will take a look into it, using (or at least starting with) the
> suggestion Sami provided.

Thanks.