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.

Sign up for GitHub

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

Jump to bottom

Track issue of merge BR into TiDB #26877

Closed
8 tasks done
3pointer opened this issue Aug 4, 2021 · 3 comments
Closed
8 tasks done

Track issue of merge BR into TiDB #26877

3pointer opened this issue Aug 4, 2021 · 3 comments
Labels
type/feature-request Categorizes issue or PR as related to a new feature.

Comments

@3pointer
Copy link
Contributor

3pointer commented Aug 4, 2021 •
edited by tisonkun
Loading

Development Task

This issue traces the effort to merge BR into TiDB.

Original discussion is on https://internals.tidb.io/t/topic/256/8
@3pointer 3pointer added the type/feature-request Categorizes issue or PR as related to a new feature. label Aug 4, 2021
@tisonkun
Copy link
Contributor

tisonkun commented Aug 4, 2021

Shall we review in order that first pingcap/kvproto#790 and then #26880 and then PingCAP-QE/ci#353?

@3pointer
Copy link
Contributor Author

3pointer commented Aug 4, 2021

Shall we review in order that first pingcap/kvproto#790 and then #26880 and then PingCAP-QE/ci#353?

Yes, After pingcap/kvproto#790, we need change the go.mod in #26880

@tisonkun
Copy link
Contributor

All subtasks done. The proposal is useless months after the merge happened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/feature-request Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@3pointer @tisonkun