Skip to content

Conversation

@sre-bot
Copy link
Contributor

@sre-bot sre-bot commented Jun 8, 2020

cherry-pick #2664 to release-3.1


What is changed, added or deleted? (Required)

Update backup-and-restore-tool.md

Which TiDB version(s) do your changes apply to? (Required)

  • master (the latest development version)
  • v4.0 (TiDB 4.0 versions)
  • v3.1 (TiDB 3.1 versions)
  • v3.0 (TiDB 3.0 versions)
  • v2.1 (TiDB 2.1 versions)

If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-4.0, needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.

What is the related PR or file link(s)?

Signed-off-by: sre-bot <sre-bot@pingcap.com>
@sre-bot sre-bot added the type/cherry-pick-for-release-3.1 This PR is cherry-picked to release-3.1 from a source PR. label Jun 8, 2020
@toutdesuite
Copy link
Contributor

@YuJuncen Please double check whether all the changes apply to v3.1, thanks

Copy link
Contributor

@YuJuncen YuJuncen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since docs-cn#3143 should be cherry-pick to 3.1(but unexpectedly not, so confused people), content here should apply to 3.1, too.

LGTM

@toutdesuite
Copy link
Contributor

I'll merge this PR when configure-placement-rules.md is manually cherry-picked to v3.1

Copy link

@shuijing198799 shuijing198799 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@yikeke
Copy link
Contributor

yikeke commented Jun 16, 2020

Since docs-cn#3143 should be cherry-pick to 3.1(but unexpectedly not, so confused people), content here should apply to 3.1, too.

LGTM

pingcap/docs-cn#3143 has been cherry-picked to 3.1 branch. FYI @YuJuncen

@yikeke
Copy link
Contributor

yikeke commented Jun 16, 2020

#2768 cherry-picked the same changes and get merged, so this PR has no files changed. FYI @toutdesuite

@yikeke yikeke added the duplicate Issues or pull requests already exists. label Jun 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

duplicate Issues or pull requests already exists. type/cherry-pick-for-release-3.1 This PR is cherry-picked to release-3.1 from a source PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants