-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: ipfs/kubo
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 3f90ef46b437^
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: ipfs/kubo
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 4c1dace86941
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 4 commits
- 2 files changed
- 1 contributor
Commits on Jun 20, 2015
-
test/sharness/t0051-object.sh: Collect OUTPUT tests together
Configuration menu - View commit details
-
Copy full SHA for 3f90ef4 - Browse repository at this point
Copy the full SHA 3f90ef4View commit details -
core/commands/object: Intermediate-node creation for patch add-link
Because: ipfs object patch $ROOT add-link a/b/c $FILE is a lot easier than: EMPTY=$(ipfs object new unixfs-dir) && A=$(ipfs object patch $EMPTY add-link b $EMPTY) && R=$(ipfs object patch $ROOT add-link a $A) && ipfs object patch $R add-link a/b/c $FILE and the long form isn't even checking to see if the original $ROOT has descendents a or a/b. Note that these are just Merkle nodes, not Unix-FS directories, because 'ipfs object ...' is a Merkle-level tool. I'd like to make this flexible enough that we could have a Unix-FS-level 'ipfs file patch ...' with similar semantics except that it operates on Unix-FS-level nodes (e.g. it creates intermediate *directories*, turns directories into files if you use 'set-data', manages the '*-data' commands without clobbering the type information unixfs stores in Data, etc.). But I don't want that Unix-FS abstraction stuff sneaking into the Merkle-level command we're working on here. License: MIT Signed-off-by: W. Trevor King <wking@tremily.us>
Configuration menu - View commit details
-
Copy full SHA for 7473870 - Browse repository at this point
Copy the full SHA 7473870View commit details -
core/commands/object: Add bubbling to rm-link
And now that we have several multi-layer patch tests, disambiguate the name of the add-without-autocreation test. License: MIT Signed-off-by: W. Trevor King <wking@tremily.us>
Configuration menu - View commit details
-
Copy full SHA for 88397ac - Browse repository at this point
Copy the full SHA 88397acView commit details -
core/commands/object: List all actions and their arguments for 'patch'
Also fix a copy/paste error in an appendDataCaller error messages so it references append-data instead of set-data. License: MIT Signed-off-by: W. Trevor King <wking@tremily.us>
Configuration menu - View commit details
-
Copy full SHA for 4c1dace - Browse repository at this point
Copy the full SHA 4c1daceView commit details
There are no files selected for viewing