On Wed, Aug 03, 2016 at 10:35:54AM -0700, Junio C Hamano wrote: > Santiago Torres <santi...@nyu.edu> writes: > > >> Submodules actually track commits, not tags or branches. > >> > >> This is confusing for some users, e.g. the user intended to track a > >> library at version 1.1, but it tracks 1234abcd instead (which is > >> what 1.1 points at). > > > > I'm assuming that git submodule update does update where the ref > > points to, does it not? > > I think you may configure the command to do so, instead of the default > "detach at the commit recorded in the superproject". > > But then your tree immediately will be marked by "git status" as > "modified" at such a submodule, meaning "what you have in the working > tree is different from what the commit in the superproject wants you > to have", I would think. >
Ah, I see where is my confusion. Thanks for the correction :) -Santiago. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
