diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawmkBwMWvNKZZCge_YqobCSILPMeK6xbFw8 <develop@web> | 2013-09-09 21:55:45 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-09-09 21:55:45 +0000 |
| commit | b1827a2289a1498251184614916a324009202f43 (patch) | |
| tree | ca1698f2412eda84a434789277db770bcbab02d2 /doc | |
| parent | 2a0ea6d33a61d8a19bb88ba9e0057a20f38b1481 (diff) | |
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/todo/Wishlist:_sanitychecker_fix_wrong_UUID__47__duplicate_remote.mdwn | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/todo/Wishlist:_sanitychecker_fix_wrong_UUID__47__duplicate_remote.mdwn b/doc/todo/Wishlist:_sanitychecker_fix_wrong_UUID__47__duplicate_remote.mdwn new file mode 100644 index 000000000..ff7773d3e --- /dev/null +++ b/doc/todo/Wishlist:_sanitychecker_fix_wrong_UUID__47__duplicate_remote.mdwn @@ -0,0 +1,7 @@ +In certain situations different client annexes might get the same remote repository added, but before being synced. + +Once the two clients sync they will both have two remotes with the same name. But only one UUID will have any content(Assuming only one client pushed). + +It would be nice to have some (automatic?) way to resolve this conflict. + +Not sure if anything sane can be done if both clients have pushed? |