confirmed
This commit is contained in:
parent
790e0083ed
commit
2f3a275b58
1 changed files with 12 additions and 3 deletions
|
@ -10,6 +10,15 @@ See [the original import tree todo for discussion about the race conditions](htt
|
||||||
Mistakes in these things can result in data loss, and it's
|
Mistakes in these things can result in data loss, and it's
|
||||||
rather subtle stuff. --[[Joey]]
|
rather subtle stuff. --[[Joey]]
|
||||||
|
|
||||||
> It may be better to implement [[importtree_only_remotes]] and make
|
What I'd like to do is implement this in concert with someone who is
|
||||||
> a simpler protocol extension that supports that, rather than supporting
|
implementing a special remote that uses it. So we can iterate on the
|
||||||
> both export and import tree together. --[[Joey]]
|
protocol as needed to make it better. --[[Joey]]
|
||||||
|
|
||||||
|
I do want to implement this though, assuming it turns out to be feasible
|
||||||
|
for people to implement it despite its complexity, so I'm tagging this confirmed.
|
||||||
|
|
||||||
|
(This is probably a prerequisite for the [[importtree_only_remotes]] idea,
|
||||||
|
although it might make sense to implement that as a simpler protocol
|
||||||
|
extension.)
|
||||||
|
|
||||||
|
[[!confirmed]]
|
||||||
|
|
Loading…
Reference in a new issue