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

fixed

Browse source
This commit is contained in:
Joey Hess 2022-07-20 13:32:26 -04:00
parent 05b96a1acf
commit a0746d2027
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/todo/registerurl__58___do_changes_in_journal___34__in_place__34____63__.mdwn
View file

@ -29,3 +29,5 @@ may be there is a way to "stagger" those --batch additions somehow so all thousa
PS More information could be found at [dandisets/issues/225](https://github.com/dandi/dandisets/issues/225 )
[[!tag projects/dandi]]
> [[fixed|done]], see my last comment for what you need to do. --[[Joey]]

20
doc/todo/registerurl__58___do_changes_in_journal___34__in_place__34____63__/comment_21_953eaa6ca651597897a6c6ad7a259d1d._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 21"""
date="2022-07-20T17:24:25Z"
content="""
I've finished implementing appending.
In order to avoid stacking up a year-long v10-v12 upgrade behind the current
v8-v10 upgrade, appending will for now only be done when
annex.alwayscompact=false. ([[todo/v11_changes]] has been made to remind
me to revisit this later.)
That config is necessary for optimal speed in your situation anyway.
You should avoid setting annex.alwayscompact=false if there is an older
git-annex also installed on the machine, that could be run in the
repository at the same time as a git-annex process that is doing appends.
Otherwise, you do risk the old process seeing partial/interrupted appends
and getting confused.
"""]]