Jakub Narebski <jnareb@xxxxxxxxx> writes:
> Additionally for each of those cases we have to consider how to compute the
> link and which commands should be modified, which commands can make use of
> the link and should be modified, should the link be to commit, tag, tree or
> blob, what we want to do with link when pulling/pushing/cloning into
> another repository and which commands should be modified. Not only use case
> scenarios.
This last paragraph is a very good suggestion. The alleged "use
cases" are just laudary list of wishes, if they are not
accompanied by descriptions on what the modified data structure
and added attribute _means_ and how they are _used_.
Here is a related but not necessarily competing idle thought.
How about an ability to "attach" arbitrary objects to commit
objects? The commit object would look like:
tree 0aaa3fecff73ab428999cb9156f8abc075516abe
parent 5a6a8c0e012137a3f0059be40ec7b2f4aa614355
parent e1cbc46d12a0524fd5e710cbfaf3f178fc3da504
related a0e7d36193b96f552073558acf5fcc1f10528917 key
related 0032d548db56eac9ea09b4ba05843365f6325b85 cherrypick
author Junio C Hamano <junkio@xxxxxxx> 1145943079 -0700
committer Junio C Hamano <junkio@xxxxxxx> 1145943079 -0700
Merge branch 'pb/config' into next
* pb/config:
Deprecate usage of git-var -l for getting config vars list
git-repo-config --list support
The format of "related" attribute is, keyword "related", SP, 40-byte
hexadecimal object name, SP, and arbitrary sequence of bytes
except LF and NUL. Let's call this arbitrary sequence of bytes
"the nature of relation".
The semantics I would attach to these "related" links are as
follows:
* To the "core" level git, they do not mean anything other than
"you must to have these objects, and objects reachable from
them, if you are going to have this commit and claim your
repository is without missing objects".
That means "git-rev-list --objects" needs to list these objects
(and if they are tags, commits, and trees, then what are
reachable from them), and "git-fsck" needs to consider these
related objects and objects reachable from them are reachable
from this commit. NOTHING ELSE NEEDS TO BE DONE by the core
(obviously, cat-file needs to show them, and commit-tree needs to
record them, but that goes without saying).
Then porcelains can agree on what different kinds of nature of
relation mean and do sensible things. The earlier "omit the
cherry-picked ones" example I gave can examine "cherrypick".
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html