BR: refine BR docs #8628
Merged
BR: refine BR docs #8628
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
ti-chi-bot
added
the
do-not-merge/work-in-progress
ti-chi-bot
added
missing-translation-status
shichun-0415
added
type/refactor
ti-chi-bot
added
the
needs-rebase
shichun-0415
force-pushed
the
refine-BR
branch
2 times, most recently
from
cef9e4b
to
1612bb1
Compare
ti-chi-bot
removed
the
needs-rebase
14 tasks
ti-chi-bot
removed
the
do-not-merge/work-in-progress
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
ti-chi-bot
added
status/LGT2
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
IANTHEREAL
reviewed
Jun 29, 2022
br/backup-and-restore-faq.md
Outdated
|
|
||
| If a backup operation fails and the preceding message occurs, perform one of the following operations and then start the backup again: | ||
|
|
||
| - Change the directory for the backup. For example, change `/dir/backup-2020-01-01/` to `/dir/backup_local/`. |
There was a problem hiding this comment.
change /dir/backup_local/ to /dir/backup-2020-01-01/?
shichun-0415
commented
Jun 29, 2022
|
/merge |
1 similar comment
|
/merge |
|
This pull request has been accepted and is ready to merge. Commit hash: 723d507
|
ti-chi-bot
added
the
status/can-merge
ti-chi-bot
pushed a commit
to ti-chi-bot/docs
that referenced
this pull request
Jun 29, 2022
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
14 tasks
|
In response to a cherrypick label: new pull request created: #9421. |
ti-chi-bot
pushed a commit
to ti-chi-bot/docs
that referenced
this pull request
Jun 29, 2022
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
14 tasks
|
In response to a cherrypick label: new pull request created: #9422. |
ti-chi-bot
added a commit
that referenced
this pull request
Jun 30, 2022
ti-chi-bot
added a commit
that referenced
this pull request
Jun 30, 2022
This was referenced Jul 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First-time contributors' checklist
What is changed, added or deleted? (Required)
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)?
Do your changes match any of the following descriptions?