diff options
author | Joey Hess <joeyh@joeyh.name> | 2016-04-21 14:24:06 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2016-04-21 14:24:06 -0400 |
commit | c120ecc00abc99bb09a7c241c0aa59bf4b47da7e (patch) | |
tree | c86a10f984af63eae2dd96efc89fbc86d476d7f8 /doc | |
parent | 1e8daf3c84170e0e54e784df549c17155121b81b (diff) |
todo
Diffstat (limited to 'doc')
-rw-r--r-- | doc/todo/support_--allow-unrelated-histories_in_git_2.8.1pre.mdwn | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/todo/support_--allow-unrelated-histories_in_git_2.8.1pre.mdwn b/doc/todo/support_--allow-unrelated-histories_in_git_2.8.1pre.mdwn new file mode 100644 index 000000000..3218c3b16 --- /dev/null +++ b/doc/todo/support_--allow-unrelated-histories_in_git_2.8.1pre.mdwn @@ -0,0 +1,15 @@ +git merge has recently been made to refuse to merge disconnected histories +unless --allow-unrelated-histories is passed. This will break uses of the +webapp, eg local pairing until git-annex is changed to pass that whenever +it runs `git merge`. + +It could also perhaps break uses of `git annex sync` where a remote with a +disconnected history is added and it's expected to merge with it. Although +in this latter case, it might be argued that the default git behavior has +changed and `git annex sync` should follow suite. + +(Also, any uses of `git pull` currently would need to +be split into a fetch and a merge in order to pass the option to the merge; +but AFAICS, git-annex never uses `git pull`) + +--[[Joey]] |