From: Edmundo Carmona Antoranz <eantoranz@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH v1] rebase - recycle
Date: Sat, 23 Apr 2022 11:17:02 +0200 [thread overview]
Message-ID: <CAOc6etYMyA3JWX7ZtvQoB2e66f7QVyabOrLTpwgP9XBRoipgfQ@mail.gmail.com> (raw)
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.
>
> 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.
next prev parent reply other threads:[~2022-04-23 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 18:37 [PATCH v1] rebase - recycle Edmundo Carmona Antoranz
2022-04-22 21:50 ` Junio C Hamano
2022-04-23 9:17 ` Edmundo Carmona Antoranz [this message]
2022-04-23 16:34 ` Junio C Hamano
2022-04-22 22:57 ` Ævar Arnfjörð Bjarmason
2022-04-23 9:12 ` Edmundo Carmona Antoranz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOc6etYMyA3JWX7ZtvQoB2e66f7QVyabOrLTpwgP9XBRoipgfQ@mail.gmail.com \
--to=eantoranz@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).