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

Cherry-pick commits from master #960

Closed
21 tasks done
njzjz opened this issue Aug 12, 2021 · 2 comments
Closed
21 tasks done

Cherry-pick commits from master #960

njzjz opened this issue Aug 12, 2021 · 2 comments
Milestone

Comments

@njzjz
Copy link
Member

njzjz commented Aug 12, 2021

It's hard to merge devel with master since the difference is too large. So I suggest cherry-pick and force-push instead.

PRs since v1.3.0 are as follows. We needs to check if a PR has been patched to devel or is out-dated.

@njzjz njzjz added this to the v2.0.0 milestone Aug 12, 2021
@njzjz
Copy link
Member Author

njzjz commented Aug 12, 2021

@denghuilu Can you make sure we can ignore #334, #407, and #424?

@denghuilu
Copy link
Member

denghuilu commented Aug 13, 2021

These three PRs can be safely ignored. #334 was out-dated, and #407,#427 have been patched into devel branch.

@njzjz njzjz closed this as completed Aug 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants