mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

fix names of new git configs

Browse source
This commit is contained in:
Joey Hess 2024-05-14 15:33:47 -04:00
parent 0722c504c5
commit 7dd2a67c41
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/git-annex.mdwn
View file

@ -1648,7 +1648,7 @@ Remotes are configured using these settings in `.git/config`.
remotes, and is set when using [[git-annex-initremote]](1) with the
`--private` option.
* `remote.<name>.max-git-bundles`, `annex.max-git-bundles`
* `remote.<name>.annex-max-git-bundles`, `annex.max-git-bundles`
When using [[git-remote-annex]] to store a git repository in a special
remote, this configures how many separate git bundle objects to store
@ -1659,7 +1659,7 @@ Remotes are configured using these settings in `.git/config`.
while preventing a new clone needing to download too many objects. Set to
0 to disable re-uploading.
* `remote.<name>.allow-encrypted-gitrepo`
* `remote.<name>.annex-allow-encrypted-gitrepo`
Setting this to true allows using [[git-remote-annex]] to push the git
repository to an encrypted special remote.

2
doc/git-remote-annex.mdwn
View file

@ -46,7 +46,7 @@ Pushes to a special remote are usually done incrementally. However,
sometimes the whole git repository (but not the annex) needs to be
re-uploaded. That is done when deleting a ref from the remote. It's also
done when too many git bundles accumulate in the special remote, as
configured by the `remote.<name>.max-git-bundles` git config.
configured by the `remote.<name>.annex-max-git-bundles` git config.
Like any git repository, a git repository stored on a special remote can
have conflicting things pushed to it from different places. This mostly