-
Notifications
You must be signed in to change notification settings - Fork 688
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
Add bit reverse example to dev-guide-unique-serial-number-generation #15748
Conversation
Oh, jenkins-docs/verify — Jenkins job failed. I'm not sure of the rules,, if any guidance I may be able to fix it myself. But I can't quite find the ruleset. |
Co-authored-by: Aolin <[email protected]>
@Oreoxmt Hi, thank you for the fix suggestion. Seems some verify is now successful but some others failed.. Sorry for the trouble.. |
Signed-off-by: Aolin <[email protected]>
@Tetsuya3850 No worries, I have fixed the issue in 056c172. Thanks for your contribution! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Oreoxmt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
/assign |
What is changed, added or deleted? (Required)
As discussed in this issue, it would be nice if we could clarify on what we mean by bit reverse. @Icemap have thankfully provided a sample to explain the same, so I just wanted to help in opening a PR to add it.
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
#15263
Do your changes match any of the following descriptions?