improve markup and man page rendering
This commit is contained in:
parent
1f467fa08f
commit
324d4a4d8c
2 changed files with 12 additions and 11 deletions
|
@ -29,14 +29,15 @@ These settings can be overridden on a per-repository basis using
|
|||
|
||||
* `annex.autocommit`
|
||||
|
||||
Set to false to prevent the git-annex assistant and git-annex sync
|
||||
Set to false to prevent the `git-annex assistant` and `git-annex sync`
|
||||
from automatically committing changes to files in the repository.
|
||||
|
||||
* `annex.resolvemerge`
|
||||
|
||||
Set to false to prevent merge conflicts in the checked out branch
|
||||
being automatically resolved by the git-annex assitant,
|
||||
git-annex sync, git-annex merge, and the git-annex post-receive hook.
|
||||
being automatically resolved by the `git-annex assitant`,
|
||||
`git-annex sync`, `git-annex merge`, and the `git-annex post-receive`
|
||||
hook.
|
||||
|
||||
* `annex.synccontent`
|
||||
|
||||
|
@ -45,15 +46,15 @@ These settings can be overridden on a per-repository basis using
|
|||
* `annex.securehashesonly`
|
||||
|
||||
Set to true to indicate that the repository should only use
|
||||
cryptographically secure hashes
|
||||
(SHA2, SHA3) and not insecure hashes (MD5, SHA1) for content.
|
||||
cryptographically secure hashes (SHA2, SHA3) and not insecure
|
||||
hashes (MD5, SHA1) for content.
|
||||
|
||||
When this is set, the contents of files using cryptographically
|
||||
insecure hashes will not be allowed to be added to the repository.
|
||||
|
||||
Also, git-annex fsck` will complain about any files present in
|
||||
Also, `git-annex fsck` will complain about any files present in
|
||||
the repository that use insecure hashes.
|
||||
|
||||
|
||||
Note that this is only read from the git-annex branch by
|
||||
`git annex init`, and is copied to the corresponding git config setting.
|
||||
So, changes to the value in the git-annex branch won't affect a
|
||||
|
|
|
@ -868,7 +868,7 @@ Like other git commands, git-annex is configured via `.git/config`.
|
|||
the repository that use insecure hashes.
|
||||
|
||||
To configure the behavior in new clones of the repository,
|
||||
this can be set in [[git-annex-config]].
|
||||
this can be set using [[git-annex-config]].
|
||||
|
||||
* `annex.maxextensionlength`
|
||||
|
||||
|
@ -1054,14 +1054,14 @@ Like other git commands, git-annex is configured via `.git/config`.
|
|||
and the git-annex post-receive hook.
|
||||
|
||||
To configure the behavior in all clones of the repository,
|
||||
this can be set in [[git-annex-config]].
|
||||
this can be set in [[git-annex-config]](1).
|
||||
|
||||
* `annex.synccontent`
|
||||
|
||||
Set to true to make git-annex sync default to syncing content.
|
||||
|
||||
To configure the behavior in all clones of the repository,
|
||||
this can be set in [[git-annex-config]].
|
||||
this can be set in [[git-annex-config]](1).
|
||||
|
||||
* `annex.debug`
|
||||
|
||||
|
@ -1633,7 +1633,7 @@ Remotes are configured using these settings in `.git/config`.
|
|||
from automatically committing changes to files in the repository.
|
||||
|
||||
To configure the behavior in all clones of the repository,
|
||||
this can be set in [[git-annex-config]].
|
||||
this can be set in [[git-annex-config]](1).
|
||||
|
||||
* `annex.startupscan`
|
||||
|
||||
|
|
Loading…
Reference in a new issue