[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: master updated (18e7bc87521 -> c71a520d1da)
|
From: |
Robert Pluim |
|
Subject: |
Re: master updated (18e7bc87521 -> c71a520d1da) |
|
Date: |
Wed, 09 Aug 2023 10:58:12 +0200 |
>>>>> On Wed, 09 Aug 2023 16:35:58 +0800, Po Lu <luangruo@yahoo.com> said:
>>
>> Which is why you should rebase in that situation, but some people
>> donʼt like rebase for reasons that I donʼt quite understand. "It was
>> slightly broken in a version of git from a decade ago" is not a valid
>> argument: emacs developers should be expected to update their
>> tools. <duck>
Po Lu> Rebase isn't possible on feature branches, AFAIK, as they demand
force
Po Lu> pushes.
You can push a deletion of the feature branch, and then repush the
rebased branch.
Robert
--
- Re: master updated (18e7bc87521 -> c71a520d1da), Stefan Kangas, 2023/08/06
- Re: master updated (18e7bc87521 -> c71a520d1da), Po Lu, 2023/08/06
- Re: master updated (18e7bc87521 -> c71a520d1da), Stefan Kangas, 2023/08/06
- Re: master updated (18e7bc87521 -> c71a520d1da), Po Lu, 2023/08/06
- Re: master updated (18e7bc87521 -> c71a520d1da), Robert Pluim, 2023/08/09
- Re: master updated (18e7bc87521 -> c71a520d1da), Po Lu, 2023/08/09
- Re: master updated (18e7bc87521 -> c71a520d1da),
Robert Pluim <=
- Re: master updated (18e7bc87521 -> c71a520d1da), Po Lu, 2023/08/09
- Re: master updated (18e7bc87521 -> c71a520d1da), Robert Pluim, 2023/08/09
- Re: master updated (18e7bc87521 -> c71a520d1da), Eli Zaretskii, 2023/08/09