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

prevent appends except when annex.alwayscompact=false

Browse source 
I would like for a new repo version to enable appends, but to do so
safely would need a v11 followed by a 1 year delay followed by a v12
that does it. Since a similar v9 and v10 transition is currently
happening, and is less than 6 months along in most repos, it does not
feel wise to stack up another year-long transition behind that. What if
I need to hurry up a new repo version for some other change?

Added todo so I remember to make this change at some time when a v11
and probably v12 repo version do make sense.

Sponsored-by: Dartmouth College's DANDI project
This commit is contained in:
Joey Hess 2022-07-20 13:19:06 -04:00
parent d275874e6c
commit 4e88137a28
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 32 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

5
doc/git-annex.mdwn
View file

@ -1051,6 +1051,11 @@ repository, using [[git-annex-config]]. See its man page for a list.)
`-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.