diff options
author | 2016-04-04 13:55:15 -0400 | |
---|---|---|
committer | 2016-04-04 13:55:15 -0400 | |
commit | d9c5096d738427cebe33c9eee1887235598b36e3 (patch) | |
tree | 462ed3cdd1ebcaf756f104ce13aff1a45cf241fe /doc/design | |
parent | cdddad27e44443177b7878821a057c6eaf16cc05 (diff) |
still bug with sync in adjusted branch
Diffstat (limited to 'doc/design')
-rw-r--r-- | doc/design/adjusted_branches.mdwn | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/doc/design/adjusted_branches.mdwn b/doc/design/adjusted_branches.mdwn index 90f880e64..28fecb2c5 100644 --- a/doc/design/adjusted_branches.mdwn +++ b/doc/design/adjusted_branches.mdwn @@ -351,6 +351,32 @@ into adjusted view worktrees.] will make copies of the content of annexed files, so this would need to checkout the adjusted branch some other way. Maybe generalize so this more efficient checkout is available as a git-annex command? +* sync in adjusted branch can trigger merge conflict detection where + there should be no conflict. + + git init a + cd a + git annex init --version=6 + touch f + git annex add f + git annex sync + cd .. + + git clone a b + cd b + git annex init --version=6 + git annex adjust --unlock + cd .. + + cd a + git mv f f2 + git annex sync + cd .. + + cd b + git annex sync + + * There are potentially races in code that assumes a branch like master is not being changed by someone else. In particular, propigateAdjustedCommits rebases the adjusted branch on top of master. |