|
@@ -37,3 +37,22 @@ A suboptimal alternative is the --explicit flag,
|
|
|
used to record only those changes done
|
|
|
to the files listed with --output flags.
|
|
|
|
|
|
+A source to clone a dataset from can also be a path,
|
|
|
+for example as in "datalad clone ../DataLad-101".
|
|
|
+
|
|
|
+Just as in creating datasets, you can add a
|
|
|
+description on the location of the new dataset clone
|
|
|
+with the -D/--description option.
|
|
|
+
|
|
|
+Note that subdatasets will not be installed by default,
|
|
|
+but are only registered in the superdataset -- you will
|
|
|
+have to do a "datalad get -n PATH/TO/SUBDATASET"
|
|
|
+to clone the subdataset for file availability meta data.
|
|
|
+The -n/--no-data options prevents that file contents are
|
|
|
+also downloaded.
|
|
|
+
|
|
|
+Note that a recursive "datalad get" would clone all further
|
|
|
+registered subdatasets underneath a subdataset, so a safer
|
|
|
+way to proceed is to set a decent --recursion-limit:
|
|
|
+"datalad get -n -r --recursion-limit 2 <subds>"
|
|
|
+
|