Merge lp:~hrvojem/percona-xtrabackup/rn-2.1.6-2.1 into lp:percona-xtrabackup/2.1
Proposed by
Hrvoje Matijakovic
Status: | Merged |
---|---|
Approved by: | Alexey Kopytov |
Approved revision: | no longer in the source branch. |
Merged at revision: | 699 |
Proposed branch: | lp:~hrvojem/percona-xtrabackup/rn-2.1.6-2.1 |
Merge into: | lp:percona-xtrabackup/2.1 |
Diff against target: |
125 lines (+59/-3) 5 files modified
doc/source/conf.py (+2/-2) doc/source/innobackupex/innobackupex_option_reference.rst (+8/-0) doc/source/installation/apt_repo.rst (+1/-0) doc/source/release-notes/2.1/2.1.6.rst (+43/-0) innobackupex.pl (+5/-1) |
To merge this branch: | bzr merge lp:~hrvojem/percona-xtrabackup/rn-2.1.6-2.1 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alexey Kopytov (community) | Approve | ||
Review via email: mp+196071@code.launchpad.net |
To post a comment you must log in.
> :option: `innobackupex --copy-back` would fail if the :option: `innodb_ data_home_ dir` was empty. Bug fixed :bug:`1049291`.
I guess it's either "the innodb_ data_home_ dir option is empty" or just "innodb_ data_home_ dir is empty", but the processed text will be "the innodb_ data_home_ dir is empty"?
> |innobackupex| wasn't able to perform backups to the ``NFS`` mount...
I'd say "to the NFS mount in some NFS configurations".
> Other bugs fixed: bug fixed :bug:`1248488`, bug fixed :bug:`1247057`, bug fixed :bug:`1250738`, bug fixed :bug:`1214274`.
Is that "bug fixed" being repeated multiple times intentional?