Skip to content

Commit

Permalink
edit the README
Browse files Browse the repository at this point in the history
  • Loading branch information
Ken Kundert authored and Ken Kundert committed Dec 18, 2021
1 parent 5248a98 commit a166ad7
Show file tree
Hide file tree
Showing 3 changed files with 1 addition and 18 deletions.
10 changes: 0 additions & 10 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -27,22 +27,12 @@ Emborg — Front-End to Borg Backup
a front-end to Borg, a powerful and fast deduplicating backup program. With
*Emborg*, you specify all the details about your backups once in advance, and
then use a very simple command line interface for your day-to-day activities.
The details are contained in ~/.config/emborg. That directory contains a file
(settings) that contains shared settings, and then another file for each backup
configuration you have.

Use of *Emborg* does not preclude the use of Borg directly on the same
repository. The philosophy of *Emborg* is to provide commands that you would
use often and in an interactive manner with the expectation that you would use
Borg directly for the remaining commands.

An alternative to *Emborg* is
`Borgmatic <https://github.com/witten/borgmatic>`_. It seems largely focused on
the archive creation process and offers little for the other management tasks
such as monitoring (*due*, *list*, *manifest*), restoration (*extract*, *restore*,
*mount*), and maintenance (*check*, *prune*). *borgmatic* recently added support
for the Borg *extract* command.


Getting Help
------------
Expand Down
7 changes: 0 additions & 7 deletions doc/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -23,13 +23,6 @@ repository. The philosophy of *Emborg* is to provide commands that you would
use often and in an interactive manner with the expectation that you would use
*Borg* directly for more unusual or esoteric situations.

An alternative to *Emborg* is
`borgmatic <https://github.com/witten/borgmatic>`_. It seems largely focused on
the archive creation process and offers little for the other management tasks
such as monitoring (*due*, *list*, *manifest*), restoration (*mount*), and
maintenance (*check*, *prune*). *borgmatic* recently added support for the
*Borg* extract command.


Why Borg?
---------
Expand Down
2 changes: 1 addition & 1 deletion doc/releases.rst
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Latest development release
-----------------
- Do not signal failure to hooks if Borg completes normally, even if there were
warnings.
- Return an exit status of 1 if *Emborg runs to completion but with exceptions,
- Return an exit status of 1 if *Emborg* runs to completion but with exceptions,
and 2 if it cannot complete normally due to a error or errors.


Expand Down

0 comments on commit a166ad7

Please sign in to comment.