diff options
| author |  ypid <ypid@web> | 2015-08-31 19:06:02 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-08-31 19:06:02 +0000 |
| commit | 41092895ac81a8e5408ff9c091e574a0bf51a5cf (patch) | |
| tree | b6e5383fcecce269e4bf658b1a893126de6498c4 /doc | |
| parent | 5cf805ff744da19adb464c6001b35b7998a4d033 (diff) | |
Fixed spelling.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/design/metadata.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/design/metadata.mdwn b/doc/design/metadata.mdwn index 9da0a3626..35e45f811 100644 --- a/doc/design/metadata.mdwn +++ b/doc/design/metadata.mdwn @@ -79,7 +79,7 @@ subdirs. # other uses for metadata -Uses are not limited to view branches. +Users are not limited to view branches. `git annex checkoutmeta year=2014 talk` in a subdir of master could create the same tree of files filter would. The user can then commit that if desired. @@ -177,7 +177,7 @@ So, possible approaches: * Metadata should be copied to the new key when adding a modified version of a file. **done** -* Filesystems that are not case sensative (including case preserving OSX) +* Filesystems that are not case sensitive (including case preserving OSX) will cause problems if view branches try to use different cases for 2 directories representing a metadata field. |