fix: update repo specs according to the current state of go-ipfs repo #186
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This has a conflict file. let me have a look, really old PR 😅 |
vasco-santos
force-pushed
the
fix-repo-specs
branch
from
92eaa23 to
58ca18e
Compare
|
@daviddias I think you can now go ahead with this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the context of the
Awesome Endeavour: Repo interoperabilityjs-ipfs#1467, here is a PR updating the specs to the current state of the repo, as specified in the issue:1) ipfs/specs
Note: I removed the
logspart since it was cancelled a long time ago (js-ipfs-repo#8).