Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport] Fix rebase conflict detection in git 2.26 (#10929) #10930

Merged

Conversation

6543
Copy link
Member

@6543 6543 commented Apr 2, 2020

backport of #10929

include:

  • 0001-Fix-rebase-conflict-detection-in-git-2.26.patch
  • 0002-As-per-techknowlogick-reduce-copying.patch

Git changed the technique used in rebase from
simple apply-patches to use merge. This breaks
our conflict detection code.

created by: Andrew Thornton <art27@cantab.net>
@zeripath zeripath added this to the 1.11.5 milestone Apr 2, 2020
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Apr 3, 2020
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Apr 3, 2020
@techknowlogick
Copy link
Member

ping LG-TM

@techknowlogick techknowlogick merged commit f7d7cf4 into go-gitea:release/v1.11 Apr 3, 2020
@zeripath zeripath deleted the backport-git2.26-fix branch April 3, 2020 18:03
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants