diff options
| author |  eigengrau <eigengrau@web> | 2015-05-31 14:30:37 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-05-31 14:30:37 +0000 |
| commit | 0be33ebb7e8c9df0300cbf0a77235eb02cd40e49 (patch) | |
| tree | bb3db0473035040f0f53865a413b4174d81f11f7 /doc/todo/Metadata_on_regular_git_objects___40__blob__44___trees__41____63__.mdwn | |
| parent | 05cb259f71bbb61a51e533105e8ef6469a0805a5 (diff) | |
Diffstat (limited to 'doc/todo/Metadata_on_regular_git_objects___40__blob__44___trees__41____63__.mdwn')
| -rw-r--r-- | doc/todo/Metadata_on_regular_git_objects___40__blob__44___trees__41____63__.mdwn | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/todo/Metadata_on_regular_git_objects___40__blob__44___trees__41____63__.mdwn b/doc/todo/Metadata_on_regular_git_objects___40__blob__44___trees__41____63__.mdwn new file mode 100644 index 000000000..b3793501a --- /dev/null +++ b/doc/todo/Metadata_on_regular_git_objects___40__blob__44___trees__41____63__.mdwn @@ -0,0 +1 @@ +Is it technically possible for the metadata interface to also support regular git objects, so that committed files or directories were also subject to tagging? For most metadata-related intents and purposes it seems I’d like to treat annexed and regular files alike; so I’d like to tag the LaTeX/ReST/etc. source for a presentation the same way I treat the output PDF, only that the former are likely not annexed. In the design docs it says metadata is attached to annex keys. Could it equally be attached to git blobs and trees, or would that break horribly somewhere? |