You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
//to get the state in a point in time we would have to find a snapshot before that time, then apply any commits that came after that snapshot but still before the point in time.
105
-
//we would probably want the most recent snapshot to always follow current, so we might need to track the number of changes a given snapshot represents so we can
106
-
//decide when to create a new snapshot instead of replacing one inline. This would be done by using the current snapshots parent, instead of the snapshot itself.
107
-
// s0 -> s1 -> sCurrent
108
-
// if always taking snapshots would become
109
-
// s0 -> s1 -> sCurrent -> sNew
110
-
//but but to not snapshot every change we could do this instead
111
-
// s0 -> s1 -> sNew
112
-
113
-
//when both snapshots are for the same commit we don't want to keep the previous, therefore the new snapshot should be root
//to get the state in a point in time we would have to find a snapshot before that time, then apply any commits that came after that snapshot but still before the point in time.
202
+
//we would probably want the most recent snapshot to always follow current, so we might need to track the number of changes a given snapshot represents so we can
203
+
//decide when to create a new snapshot instead of replacing one inline. This would be done by using the current snapshots parent, instead of the snapshot itself.
204
+
// s0 -> s1 -> sCurrent
205
+
// if always taking snapshots would become
206
+
// s0 -> s1 -> sCurrent -> sNew
207
+
//but but to not snapshot every change we could do this instead
208
+
// s0 -> s1 -> sNew
209
+
210
+
//when both snapshots are for the same commit we don't want to keep the previous, therefore the new snapshot should be root
0 commit comments