[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: master updated (18e7bc87521 -> c71a520d1da)
From: |
Po Lu |
Subject: |
Re: master updated (18e7bc87521 -> c71a520d1da) |
Date: |
Wed, 09 Aug 2023 17:16:14 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Robert Pluim <rpluim@gmail.com> writes:
> You can push a deletion of the feature branch, and then repush the
> rebased branch.
I don't think the 3 or 4 individuals tracking the feature/android branch
would have taken kindly to such a gesture. (Not merging at all wasn't
an option either, since the branch saw active use.)
Can't the Git people fix this by excluding merge commits from merges
themselves, or something?
- 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, 2023/08/09
- Re: master updated (18e7bc87521 -> c71a520d1da),
Po Lu <=
- Re: master updated (18e7bc87521 -> c71a520d1da), Robert Pluim, 2023/08/09
- Re: master updated (18e7bc87521 -> c71a520d1da), Eli Zaretskii, 2023/08/09