From: Junio C Hamano <gitster@pobox•com>
To: Edmundo Carmona Antoranz <eantoranz@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [RFC] introducing git replay
Date: Wed, 13 Apr 2022 10:05:03 -0700 [thread overview]
Message-ID: <xmqq4k2wap8g.fsf@gitster.g> (raw)
In-Reply-To: <20220413164336.101390-1-eantoranz@gmail.com> (Edmundo Carmona Antoranz's message of "Wed, 13 Apr 2022 18:43:35 +0200")
Edmundo Carmona Antoranz <eantoranz@gmail•com> writes:
> This is a RFC because:
> - Perhaps it is already possible to do it with git rebase
> to achieve the same? But I haven't seen a recipe that
> gets it done in stackoverflow, at least.
Without thinking about it too much, out of gut reaction, it looks
like a better target for fast-export piped to fast-import than
rebase or amend, if all it can do is to replay on _identical_ state
and nothing else.
> Let me know what you think.
> Interesting? Not?
If this _were_ to allow some slight deviations of the base and carry
the differences forward, then it definitely belongs to rebase, and
perhaps "rebase --replay-merges" should be taught to behave better
without introducing a new option. But otherwise, I do not think it
is all that useful.
Also, if this _were_ to allow recreating the shape of the history,
using updated tips of branches that were merged in the original
history, perhaps taking hints from "Merge branch X into Y" in the
original merge commit's log messages, that would be quite useful
addition to the rebase mechanism, but this is not that.
So, not really, to me at least.
next prev parent reply other threads:[~2022-04-13 17:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 16:43 [RFC] introducing git replay Edmundo Carmona Antoranz
2022-04-13 17:05 ` Junio C Hamano [this message]
2022-04-15 18:46 ` Edmundo Carmona Antoranz
2022-04-15 20:33 ` Junio C Hamano
2022-04-16 5:35 ` Edmundo Carmona Antoranz
2022-04-16 6:39 ` Junio C Hamano
2022-04-16 7:02 ` Edmundo Carmona Antoranz
2022-04-17 5:05 ` Elijah Newren
2022-04-17 5:37 ` Edmundo Carmona Antoranz
2022-04-17 17:22 ` Martin von Zweigbergk
2022-04-18 7:04 ` Edmundo Carmona Antoranz
2022-04-18 7:29 ` Sergey Organov
2022-04-18 16:27 ` Elijah Newren
2022-04-18 17:33 ` Sergey Organov
2022-04-20 11:27 ` Tao Klerks
2022-04-21 2:33 ` Elijah Newren
2022-04-13 17:26 ` rsbecker
2022-04-13 17:30 ` Edmundo Carmona Antoranz
2022-04-13 17:44 ` Edmundo Carmona Antoranz
2022-04-13 17:44 ` Phillip Susi
2022-04-13 17:49 ` Edmundo Carmona Antoranz
2022-04-13 19:07 ` Ævar Arnfjörð Bjarmason
2022-04-13 17:48 ` Junio C Hamano
2022-04-13 17:56 ` Edmundo Carmona Antoranz
2022-04-13 20:06 ` Eric Sunshine
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq4k2wap8g.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=eantoranz@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox