Am 26.01.2011 20:10, schrieb Julian Ibarz: > On Wed, Jan 26, 2011 at 2:06 PM, Jens Lehmann <Jens.Lehmann@xxxxxx> wrote: >> Am 26.01.2011 19:32, schrieb Julian Ibarz: >>> I am using git submodule in one of my professional projects and I am >>> facing an issue when I am using git bisect in one of the submodules. >>> >>> Basically I have a meta repository which I will call A and two >>> submodules B and C. Sometimes I use git bisect in B but it is >>> dependent on C so when I go back too much in the history of B, C needs >>> to change its version to a compatible one. Doing this manually is >>> really time consuming for me and I guess a lot of people have this >>> issue so I was a little bit surprise to not find easily anything on >>> the net that permits to do this automatically. >> >> What about bisecting in A (doing "git submodule update" after every >> step) to bisect to a smaller range of commits in B (which are then >> not dependent on your submodule C anymore and can be bisected inside >> B)? This of course assumes A properly records the dependencies >> between B and C. > > Yes but actually my real use case that made me write this mail was > more I have a feature done in an old branch and to try it I never to > revert back to this version. In this case, I have to find out the > corresponding good version in A and C. In this case I cannot start > like what you propose in A to find out the good version in B and C, I > already know the version I want in B. 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? >>> Is there anything existing to do that and I just didn't find it yet? >>> If not I think I might have an implementation idea I would like to try >>> out. >> >> The call to "git submodule update" after each bisect step in the >> superproject will be obsolete as soon as the recursive checkout >> I am currently working on is done, but that is not here yet. > > Can you be more detailed about your recursive checkout feature? Is it > what I proposed? I don't think so, that will just get rid of the extra call to "git submodule update" when bisecting in A. -- 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