Am 26.01.2011 20:48, schrieb Julian Ibarz: > Basically my feature would work like this: > > in B: > git submodule checkout some_version > > This will checkout B but also change A and C so that it is compatible > with some_version of B. Basically it will find the commit in A that > has the closest parent commit of some_version in B. When this is done > it just does git submodule udate on other submodules. Thanks, now I understand what you are trying to achieve. > I see in gitk that there is a feature that has a common implementation > for what I want to do: > > For every commits you can see Follows and Precedes which lists the > closest label before this release and after. What I need is the same > thing: instead of finding a closest labeled commit, I need to find a > closest commit referenced by A that precedes current HEAD of B. When > this is done I know which commit A has to be and then just have to > call git submodule update in A (update every other submodules except > for B). I am not aware of something like that in current Git, But I see that such functionality would be helpful. Care to share your implementation idea? -- 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