Re: Updating a submodule with a compatible version from another submodule version using the parent meta-repository
- From
Jens Lehmann <jens.lehmann@web.de>
- Date
- Jan 26, 2011, 20:31 UTC
- Message-ID
- <4D40849C.2050903@web.de>
- In-Reply-To
- <AANLkTik-XdgGM20kFu8KZ5k9ynfNAo8fvL9t7kL_JhQg@mail.gmail.com>
Am 26.01.2011 20:48, schrieb Julian Ibarz:
Show 9 quoted lines
> 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.
Show 10 quoted lines
> 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?