Skip to content
This repository has been archived by the owner on Mar 10, 2020. It is now read-only.

Commit

Permalink
docs: clarify MFS cp/mv from IPFS path (#550)
Browse files Browse the repository at this point in the history
Copying or moving from an IPFS path does _not_ recursively retrieve all contents from the network if not in your node's repo - it only retrieves the root node.
  • Loading branch information
Alan Shaw authored Oct 31, 2019
1 parent 7bb237d commit 3b4a76c
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions SPEC/FILES.md
Original file line number Diff line number Diff line change
Expand Up @@ -786,6 +786,8 @@ If `from` has a single value and `to` exists and is a file, `from` must be a fil

If `from` is an IPFS path, and an MFS path exists with the same name, the IPFS path will be chosen.

If `from` is an IPFS path and the content does not exist in your node's repo, only the root node of the source file with be retrieved from the network and linked to from the destination. The remainder of the file will be retrieved on demand.

**Returns**

| Type | Description |
Expand Down Expand Up @@ -1071,6 +1073,8 @@ If `from` has a single value and `to` exists and is a file, `from` must be a fil

If `from` is an IPFS path, and an MFS path exists with the same name, the IPFS path will be chosen.

If `from` is an IPFS path and the content does not exist in your node's repo, only the root node of the source file with be retrieved from the network and linked to from the destination. The remainder of the file will be retrieved on demand.

All values of `from` will be removed after the operation is complete unless they are an IPFS path.

**Returns**
Expand Down

0 comments on commit 3b4a76c

Please sign in to comment.