From: Julian Ibarz Date: Wed, 26 Jan 2011 20:45:38 GMT Subject: Re: Updating a submodule with a compatible version from another submodule version using the parent meta-repository Message-ID: In-Reply-To: <7v7hdrl7nw.fsf@alter.siamese.dyndns.org> On Wed, Jan 26, 2011 at 3:41 PM, Junio C Hamano wrote: > Julian Ibarz writes: > >>> Hmm, looks like I lost you here ... you want to bisect in B although >>> you know what commit you want there? Care to explain a bit more? >> >> In B I have a feature to integrate in master branch. This feature is >> in branch old_feature. But this branch is really old. To try this >> feature I need to rebuild it at this version. To make the build >> success I need also to revert back the submodule C because B is >> dependent on it. But finding the good version of C that match >> old_feature version is a pain... Is it clear? > > That sounds like bisecting in C with a frozen checkout of B to see which > version in C works well with that target commit in B you know you want to > use.  Why do you need to bisect in B??? > Forget about bisect. This is a different use case where I need the feature I am talking about: checkout an old version in B and automatically having A and C switch to a compatible version (the cause can be because of a bisect or just because I want to try an old feature not yet integrated into master or whatever the reason I want to be on this old version).