borg/docs/usage/change-passphrase.rst.inc

.. IMPORTANT: this file is auto-generated from borg's built-in help, do not edit!

.. _borg_change-passphrase:

borg change-passphrase
----------------------
::

    borg change-passphrase <options> REPOSITORY

positional arguments
    REPOSITORY


`Common options`_
    |

Description
~~~~~~~~~~~

The key files used for repository encryption are optionally passphrase
protected. This command can be used to change this passphrase.
update usage files 2016-07-05 23:30:08 +02:00			`.. IMPORTANT: this file is auto-generated from borg's built-in help, do not edit!`

commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384 2015-11-13 10:42:16 -05:00			`.. _borg_change-passphrase:`

			`borg change-passphrase`
			`----------------------`
			`::`

Better help texts and Sphinx reproduction of usage - Group options - Nicer list of options in Sphinx - Deduplicate 'Common options' (including --help) The latter is done by explicitly declaring --help in the common_parser, which is then inherited by the sub-parsers; no change in observable behaviour. 2016-04-10 01:28:18 +02:00			`borg change-passphrase <options> REPOSITORY`

			`positional arguments`
			`REPOSITORY`


			`Common options`_
			`\|`

commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384 2015-11-13 10:42:16 -05:00			`Description`
			`~~~~~~~~~~~`

			`The key files used for repository encryption are optionally passphrase`
			`protected. This command can be used to change this passphrase.`