mirror/borg
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2024-12-26 09:47:58 +00:00
Code Issues Releases Wiki Activity
borg/docs/api.rst

96 lines
1.5 KiB
ReStructuredText
Raw Normal View History

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 15:42:16 +00:00
API Documentation
=================
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.archiver
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.upgrader
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.archive
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.fuse
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.platform
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.locking
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 15:42:16 +00:00
:members:
:undoc-members:
ran setup.py build_api
2016-01-23 19:52:04 +00:00
.. automodule:: borg.shellpattern
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.repository
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.lrucache
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.remote
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 15:42:16 +00:00
:members:
:undoc-members:
ran setup.py build_api
2016-01-23 19:52:04 +00:00
.. automodule:: borg.hash_sizes
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.xattr
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.helpers
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.cache
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.key
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.logger
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.platform_darwin
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.platform_linux
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.hashindex
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.compress
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.chunker
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.crypto
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 15:42:16 +00:00
:members:
:undoc-members:
ran build_api and build_usage
2015-12-13 14:47:03 +00:00
.. automodule:: borg.platform_freebsd
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 15:42:16 +00:00
:members:
:undoc-members:
Reference in a new issue Copy permalink