Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-interleaving Private History Protocol #5

Closed
Tracked by #2 ...
matheus23 opened this issue Dec 6, 2022 · 0 comments
Closed
Tracked by #2 ...

Non-interleaving Private History Protocol #5

matheus23 opened this issue Dec 6, 2022 · 0 comments
Labels

Comments

@matheus23
Copy link
Member

matheus23 commented Dec 6, 2022

Summary

Incorporate possible improvements into how the private history works so traversing history and conflict reconciliation can become better.

Problem / Need / Opportunity

To improve the file system conflict reconciliation, we need a very detailed view of file system history. There should not be any "interleaving anormalies" in the history when merging private file systems.

Success Scenario

Merging the private file system 'feels' pretty much like conflict resolution in the public file system.
It's possible to walk through the history of a single private file across revisions and maintain the same history 'track'.

ETA: 2023-03-31

@matheus23 matheus23 added this to Roadmap Dec 2, 2022
@matheus23 matheus23 converted this from a draft issue Dec 6, 2022
@matheus23 matheus23 changed the title Improved History API Improved Private History Protocol Dec 7, 2022
@matheus23 matheus23 changed the title Improved Private History Protocol Fixed Interleaving Anormalies in Private History Dec 7, 2022
@matheus23 matheus23 changed the title Fixed Interleaving Anormalies in Private History Non-interleaving Private History Protocol Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Q1 2023: Data Format Stability
Development

No branches or pull requests

2 participants