On Sat, Nov 25, 2006 at 01:53:38AM -0500, Shawn Pearce wrote: > Yann Dirson <ydirson@xxxxxxxxxx> wrote: > > We don't need to have commits in the tree for this. We'll just have > > submodule commits which are not attached to a supermodule commit, and we > > can access the whole submodule history through the submodule .git/HEAD, > > just like we do for a standard git project. > > No. You cannot do that. > > How do we setup .git/HEAD when bisecting the supermodule? > Or merging it? Or doing anything else with it? Would there be any problem assuming git-update-ref would take care of updating it ? > Ideally the .git/HEAD of every submodule should seek to the commit > that points at the tree of the submodule which the supermodule > is referencing. You mean, whenever we seek the HEAD of the supermodule, right ? > This lets you then perform a bisect within the > submodule when you identify the supermodule commit which caused > the breakage. That is, first bisect the supermodule (which naturally bisects the submodule with rough granularity, assuming there are many submodule commits for at least some supermodule commits), then bisect the submodule between the two commits identified at supermodule level, right ? > We need the submodule commits to do this. Doing it without is > too expensive. Maybe I missed something again, but I'm still not convinced :) -- Yann. - 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