diff options
author | Patrick J Cherry <patrick@bytemark.co.uk> | 2015-12-02 13:45:53 +0000 |
---|---|---|
committer | Patrick J Cherry <patrick@bytemark.co.uk> | 2015-12-02 13:45:53 +0000 |
commit | 491e9c5399f51fa0fbc93332d79a373e50a9205c (patch) | |
tree | 74c12a8f1ddf5a7776710e3cd524e749634f913b /debian/control | |
parent | b9679fd5685533fb331a2f0489004cfd34b2d80b (diff) |
Removed leading spaces from description in debian/control
Diffstat (limited to 'debian/control')
-rw-r--r-- | debian/control | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/debian/control b/debian/control index b359a0e..4a0e87b 100644 --- a/debian/control +++ b/debian/control @@ -13,17 +13,17 @@ Package: byteback Architecture: all Depends: ${shlibs:Depends}, ${misc:Depends}, ruby | ruby-interpreter, rsync, openssh-client, ruby-ffi | libffi-ruby Description: Maintenance-free client & server backup scripts for Linux - byteback encapsulates Bytemark's "best practice" for maintenance-free backups - with easy client and server setup. - . - "Maintenance-free" means that we'd rather make full use of a fixed amount of - disc space. Management of disc space must be completely automatic, so the - process never grinds to a halt for reasons that could be automatically - resolved. Failed backups can be restarted in case of network problems. - . - We use the standard OpenSSH on the server for encrypted transport & access - control, btrfs for simple snapshots and rsync for efficient data transfer - across the network. - . - Backups should require as little configuration as possible to be safe - just - the server address should be enough. + byteback encapsulates Bytemark's "best practice" for maintenance-free backups + with easy client and server setup. + . + "Maintenance-free" means that we'd rather make full use of a fixed amount of + disc space. Management of disc space must be completely automatic, so the + process never grinds to a halt for reasons that could be automatically + resolved. Failed backups can be restarted in case of network problems. + . + We use the standard OpenSSH on the server for encrypted transport & access + control, btrfs for simple snapshots and rsync for efficient data transfer + across the network. + . + Backups should require as little configuration as possible to be safe - just + the server address should be enough. |