-
Notifications
You must be signed in to change notification settings - Fork 50
Implement expiration of snapshots #636
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
Conversation
|
Some tasks that will come in future PRs:
|
66383b1 to
00db21c
Compare
| } | ||
|
|
||
| /// Cretase a new `Snapshot` with all the same data as `self` but a different parent | ||
| pub fn adopt(&self, parent: &Snapshot) -> Self { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love the name
| /// ancestry. Any other snapshots are not touched. | ||
| /// | ||
| /// The operation will edit in place the oldest non-expired snapshot, | ||
| /// changing its parent to be the root of the repo. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This means the initial commit snapshot is always the parent right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exactly, yes, the root of the repo will become the new parent of the first non-expired snapshot
|
This is so cool and really easy to read |
d2a8f4a to
d0279d3
Compare
00db21c to
84101d5
Compare
Also fix a bug where we were listing deleted tags. Some minimal refactoring too.
84101d5 to
9986d59
Compare
Also fix a bug where we were listing deleted tags.
Some minimal refactoring too.