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

Merge branch 'append'

Browse source
This commit is contained in:
Joey Hess 2022-07-20 13:24:04 -04:00
commit 05b96a1acf
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
9 changed files with 194 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/git-annex.mdwn
View file

@ -1038,6 +1038,24 @@ repository, using [[git-annex-config]]. See its man page for a list.)
This works well in combination with annex.alwayscommit=false,
to gather up a set of changes and commit them with a message you specify.
* `annex.alwayscompact`
By default, git-annex compacts data it records in the git-annex branch.
Setting this to false avoids doing that compaction in some cases, which
can speed up operations that populate the git-annex branch with a lot
of data. However, when used with operations that overwrite old values in
the git-annex branch, that may cause the git-annex branch to use more disk
space, and so slow down reading data from it.
An example of a command that can be sped up by using
`-c annex.alwayscompact=false` is `git-annex registerurl --batch`,
when adding a large number of urls to the same key.
This option was first supported by git-annex version 10.20220724.
It is not entirely safe to set this option in a repository that may also
be used by an older version of git-annex at the same time as a version
that supports this option.
* `annex.allowsign`
By default git-annex avoids gpg signing commits that it makes when

12
doc/todo/v11_changes.mdwn Normal file
View file

@ -0,0 +1,12 @@
This is a todo for collecting changes that could lead to a v11 repository
version.
* Append to journal files even when annex.alwayscompact=true.
This can make it a lot faster in some cases.
See note in Annex.Branch.changeOrAppend.
It's important that this only happen when no git-annex version
older than 10.20220724 can plausibly be running in a repository
after upgrading to the repo version that enables this. Depending on the
timing of v11, this may need to be put in a v12 upgrade that is delayed
some amount of time (eg 1 year) after v11.