On Tuesday 10 April 2007, Linus Torvalds wrote:So this does mean that the SHA1 of a gitlink entry corresponds to the commit in the subproject? I wonder if it is not useful to be able to add some attribute(s) to a gitlink, i.e. first reference a gitlink object in the superproject, which then references the submodule commit, and also holds some further attributes. These attributes can not be put into the subproject, as it should be independent. An example for such an attribute would be a subproject name/ID. An argument for this: The user should be able to specify some policies for submodules, like "do not clone/checkout this submodule". But the path where the submodule resides in a given commit is not useful here, as a submodule can reside at different paths in the history of the supermodule. Josef - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Andrew Morton | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Linus Torvalds | Linux 2.6.27-rc5 |
| David Miller | Re: [PATCH] net: Fix the prototype of call_netdevice_notifiers |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
