"rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files
Go azure-blobazure-blob-storageazure-filesbackblaze-b2cloud-storagedropboxencryptionftpfuse-filesystemgogolanggoogle-cloud-storagegoogle-driveonedriveopenstack-swiftrclones3sftpsyncwebdav
lsf: document Google Drive shortcut IDs - fixes #7863
Giridharcaf3d1cc3cb2
diff --git a/cmd/lsf/lsf.go b/cmd/lsf/lsf.goindex 03a7d9f0c..66e0fca2a 100644--- a/cmd/lsf/lsf.go+++ b/cmd/lsf/lsf.go@@ -80,6 +80,12 @@ T - tier of storage if known, e.g. "Hot" or "Cool"M - Metadata of object in JSON blob format, eg {"key":"value"}` + "```" + `+Some backends use composite IDs. In particular, Google Drive shortcuts are+normally dereferenced, and their "i" field contains the target object's ID+followed by the shortcut's ID, separated by a tab. This tab is part of the ID+field and is not changed by ` + "`--separator`" + `. Use ` + "`--drive-skip-shortcuts`" + ` to omit+shortcut entries.+So if you wanted the path, size and modification time, you would use` + "`--format \"pst\"`, or maybe `--format \"tsp\"`" + ` to put the path last.