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

Commit 3b4a76c

Browse files
author
Alan Shaw
authored
docs: clarify MFS cp/mv from IPFS path (#550)
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.
1 parent 7bb237d commit 3b4a76c

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

SPEC/FILES.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -786,6 +786,8 @@ If `from` has a single value and `to` exists and is a file, `from` must be a fil
786786

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

789+
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.
790+
789791
**Returns**
790792

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

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

1076+
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.
1077+
10741078
All values of `from` will be removed after the operation is complete unless they are an IPFS path.
10751079

10761080
**Returns**

0 commit comments

Comments
 (0)