improve documentation
This commit is contained in:
parent
452ea0ff91
commit
618b1d2a38
2 changed files with 10 additions and 3 deletions
|
@ -83,3 +83,8 @@ The following script (available at <https://gist.github.com/gioele/5ffeff8988a53
|
|||
### What version of git-annex are you using? On what operating system?
|
||||
|
||||
git-annex version: 5.20140708-g8c9c55c on Ubuntu 12.04.4
|
||||
|
||||
> I have improved the documentation to not imply that sync/merge are a
|
||||
> special case. They honor the autocommit settings more or less
|
||||
> intentionally, and to get a commit to be made, just pass -c
|
||||
> autocommit=true when running them. --[[Joey]]
|
||||
|
|
|
@ -1398,9 +1398,11 @@ Here are all the supported configuration settings.
|
|||
* `annex.alwayscommit`
|
||||
|
||||
By default, git-annex automatically commits data to the git-annex branch
|
||||
after each command is run. To disable these commits,
|
||||
set to `false`. Then data will only be committed when
|
||||
running `git annex merge` (or by automatic merges) or `git annex sync`.
|
||||
after each command is run. If you have a series
|
||||
of commands that you want to make a single commit, you can
|
||||
run the commands with `-c annex.alwayscommit=false`. You can later
|
||||
commit the data by running `git annex merge` (or by automatic merges)
|
||||
or `git annex sync`.
|
||||
|
||||
* `annex.delayadd`
|
||||
|
||||
|
|
Loading…
Reference in a new issue