Derek Fawcus wrote: > My other hacky thought was that tag object could be overloaded for > this purpose. It is already sort of an indirect object, but seems > to be limited to appearing at the edge of the graph. > > If we could say have: > > commit -> tag -> tree > > then arbitrary data could be stored in the tag, similarly this > could be extended for when a tree or blob object is expected > (I'm not sure about the blob case). I was under the impression that tags were references to commit objects, and they to tree objects: tag -> commit -> tree Also, wouldn't this require large numbers tags, or the ability to multi- target tags? -- Marcus Griep GPG Key ID: 0x5E968152 —— http://www.boohaunt.net את.ψο´ -- To unsubscribe from this list: 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
