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

devblog

Browse source
This commit is contained in:
Joey Hess 2019-04-30 16:33:48 -04:00
parent 28b4310abe
commit 8f9457dec8
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/devblog/day_585__not_matching_S3_histories.mdwn Normal file
View file

@ -0,0 +1,16 @@
I could not find a good solution to the S3 history matching problem, so I
think that was the wrong approach. Now I have what seems to be a better
approach implemented: When an import of history from S3 contains some trees
that differ from the trees that were exported to S3, all git-annex needs to
do is make git aware of that, and it can do so by making the remote
tracking branch contain a merge between what was exported to S3 and what
was imported from it.
That does mean that there can be some extra commits generated form an
import, with the same trees as commits that the user made, but a different
message. That seems acceptable. Less so is that repeated imports generate
different commits each time; I need to make it generate stable commits. I
should also add back detection of the simple fast-forward case which was
working but got broken today.
So still not done with this, but the end is in sight!