borgbackup/docs/usage/debug-put-obj.rst.inc

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

.. _borg_debug-put-obj:

borg debug-put-obj
------------------
::

    borg debug-put-obj <options> REPOSITORY PATH

positional arguments
    REPOSITORY
        repository to use
    PATH
        file(s) to read and create object(s) from

`Common options`_
    |

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

This command puts objects into the repository.
update usage files 2016-07-05 17:30:08 -04: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_debug-put-obj:`

			`borg debug-put-obj`
			`------------------`
			`::`

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-09 19:28:18 -04:00			`borg debug-put-obj <options> REPOSITORY PATH`

			`positional arguments`
			`REPOSITORY`
			`repository to use`
			`PATH`
			`file(s) to read and create object(s) from`

			`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`
			`~~~~~~~~~~~`

			`This command puts objects into the repository.`