Diff
1diff --git a/README.md b/README.md
2index dc148915adc9fa7e013cadb5dc38e278811711b4..65f9c3aba706bf2b383e90f4716c4149bb90ae40 100644
3--- a/README.md
4+++ b/README.md
5@@ -10,6 +10,10 @@ Optionally, you can set up an email address where the log file will be sent, whi
6
7 This version is a rewriting of the code originally written by [Damon Timm](https://github.com/thornomad), including many patches that have been brought to the original scripts by various forks on Github. Thanks to all the contributors!
8
9+More information about this script is available at https://zertrin.org/projects/duplicity-backup/
10+
11+The original version of the code is available at https://github.com/theterran/dt-s3-backup
12+
13
14 ## duplicity-backup.sh IS NOT duplicity
15
16@@ -29,9 +33,23 @@ Latest version of the code is available at https://github.com/zertrin/duplicity-
17
18 Pull requests are welcome! However please **always use individual feature branches for each pull request**. I may not accept a pull request from a master branch.
19
20-More information about this script is available at https://zertrin.org/projects/duplicity-backup/
21+Here is how to do it:
22
23-The original version of the code is available at https://github.com/theterran/dt-s3-backup
24+Fork the repository and then clone your fork:
25+
26+ git clone git@github.com:YOURNAME/duplicity-backup.git
27+
28+Create a new topic branch for the changes you want to make, based on the master branch from the clone:
29+
30+ git checkout -b my-fix-1 origin/master
31+
32+Make your changes, test them, commit them and push them to Github:
33+
34+ git push origin my-fix-1
35+
36+Open a Pull request from `YOURNAME:my-fix-1` to `zertrin:master`.
37+
38+If you want to open another pull request for another change which is independant of the previous one, just create another topic branch based on master (`git checkout -b my-fix-2 origin/master`)
39
40
41 ## Installation