-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
fsrepo cleanup: no more components #916
Conversation
// EventlogComponent.Close was never called. Preserving here | ||
// pending further discussion. | ||
// | ||
// TODO It isn't part of the current contract, but callers may like for us |
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.
good point
This LGTM. @tv42 just gave you contributor access so that you can push branches onto the main repo. our jenkins doesn't pick them up otherwise, so not all tests ran here. |
@tv42 btw if you have a better way of doing what he pkg-level lock/counters are doing, go for it. i don't remember the intricacy there, but things will get simpler when the cli does not need to touch the config at all. (this will be fixed when repo implements https://github.com/ipfs/specs/tree/master/repo/fs-repo#api ) |
Closing in favor of #917 |
@jbenet Yeah I was eyeing those, but decided to go for a more mechanical transformation of the source for now, to not break anything. |
This simplifies fsrepo to prepare for future changes. The should be no change in behavior.