Re: Dead-end Situation created by amending a merge commit in a topic branch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Hans,

On Sat, 15 Oct 2022, Hans Meiser wrote:

> It looks like it's possible to reach an unresolvable dead-end situation by amending a merge commit.
>
> For a use-case see this issue at Stack Overflow:
> https://stackoverflow.com/questions/74032523/how-can-i-rebase-this-git-branch-on-master/74064773

Please note that readers such as myself make a habit of not following
links thrown into a mail on the Git mailing list.

If you can summarize the problem succinctly and comprehensively, please do
so, without sending readers to read through threads elsewhere and weeding
out the relevant information for themselves. It's a better use of
everybody's time if _one_ person distills the information into a
well-written bug report, instead of forcing every reader to do that.

Ciao,
Johannes

>
> Is this situation desired?
>
> Shouldn't git rather emit an error message when trying to amend a merge commit?




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux