Re: [PATCH v1] rebase - recycle

From: Edmundo Carmona Antoranz <eantoranz@gmail.com>
Date: Apr 23, 2022, 09:17 UTC
Message-ID: <CAOc6etYMyA3JWX7ZtvQoB2e66f7QVyabOrLTpwgP9XBRoipgfQ@mail.gmail.com>
In-Reply-To: <xmqqsfq46b4p.fsf@gitster.g>

On Fri, Apr 22, 2022 at 11:50 PM Junio C Hamano <gitster@pobox.com> wrote:

>
>
> That way, you do not even need to add a single line of
> documentation, even though you still need to have tests.

Thank you for putting the time to think about it. I will take all that input to turn it into a full optimization without user intervention and see how it looks.

Show 10 quoted lines

>
> The last thing I want to hear from contributors in the open source
> development setting: I'll polish it more if you promise this will be
> included.
>
> If it is NOT even interesting and useful enough to make you want to
> polish and perfect it, even when you were the only user, why should
> we be interested?  Even if your userbase starts at zero (or one,
> counting yourself), if you make it so good, other people will come
> to you, begging you to add that to the public tool.

That is on top of "let's fork this project"? That is saying something :-D (point taken, just in case).

Given your feedback, I _think_ there is a window of opportunity for this? Let me give it a shot. I will first try to create an equivalent of this technique into a per-commit basis to make a broader usecase and see if has an impact (performance or avoiding conflicts for merges). Will let you know.