2Shirt/duplicity-backup.sh
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Bump version to 1.4.1

Browse source
This commit is contained in:
zertrin 2017-10-03 22:18:02 +08:00
parent 0c4f2b7c45
commit 98bcf9f673
3 changed files with 11 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
CHANGELOG
View file

@ -2,6 +2,10 @@ vX.X.X (unreleased)
===================
* Placeholder for next release
v1.4.1 (2017-10-04)
===================
* Show program versions in output.
v1.4.0 (2017-09-24)
===================
* Add version check of duplicity to handle deprecation of --include-globbing-filelist

9
README.md
View file

@ -80,8 +80,11 @@ If you prefer the stable version do:
Or just download the ZIP file:
* For the stable branch: https://github.com/zertrin/duplicity-backup.sh/archive/stable.zip
* For the normal branch: https://github.com/zertrin/duplicity-backup.sh/archive/master.zip
| Version | Download link |
|---------------|-------------------------------------------------------------------|
| stable | https://github.com/zertrin/duplicity-backup.sh/archive/stable.zip |
| normal | https://github.com/zertrin/duplicity-backup.sh/archive/master.zip |
| bleeding-edge | https://github.com/zertrin/duplicity-backup.sh/archive/dev.zip |
### 2. Configure the script
@ -94,7 +97,7 @@ The script looks for its configuration by reading the path to the config file sp
If no config file was given on the command line, the script will try to find the file specified in the `CONFIG` parameter at the beginning of the script (default: `duplicity-backup.conf` in the script's directory).
So be sure to either:
* specify the configuration file path on the command line with the -c option **[recommended]**
* specify the configuration file path on the command line with the `-c` option **[recommended]**
* or to edit the `CONFIG` parameter in the script to match the actual location of your config file. **[deprecated]** _(will be removed in future versions of the script)_
NOTE: to ease future updates of the script, you may prefer NOT to edit the script at all and to specify systematically the path to your config file on the command line with the `-c` or `--config` option.

2
VERSION
View file

@ -1 +1 @@
v1.4.0
v1.4.1