From: Junio C Hamano <gitster@pobox.com>
To: Julian Ibarz <julian.ibarz@gmail.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>, git@vger.kernel.org
Subject: Re: Updating a submodule with a compatible version from another submodule version using the parent meta-repository
Date: Wed, 26 Jan 2011 12:41:23 -0800 [thread overview]
Message-ID: <7v7hdrl7nw.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <AANLkTik-XdgGM20kFu8KZ5k9ynfNAo8fvL9t7kL_JhQg@mail.gmail.com> (Julian Ibarz's message of "Wed\, 26 Jan 2011 14\:48\:14 -0500")
Julian Ibarz <julian.ibarz@gmail.com> 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???
next prev parent reply other threads:[~2011-01-26 20:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinN1XVsAZXGLqkuhysrJ8-TCtGm4pOu2RfCEVVp@mail.gmail.com>
2011-01-26 18:32 ` Updating a submodule with a compatible version from another submodule version using the parent meta-repository Julian Ibarz
2011-01-26 19:06 ` Jens Lehmann
2011-01-26 19:10 ` Julian Ibarz
2011-01-26 19:39 ` Jens Lehmann
2011-01-26 19:48 ` Julian Ibarz
2011-01-26 20:31 ` Jens Lehmann
2011-01-26 20:43 ` Julian Ibarz
2011-01-26 20:41 ` Junio C Hamano [this message]
2011-01-26 20:45 ` Julian Ibarz
2011-01-26 22:05 ` Junio C Hamano
2011-01-29 11:08 ` Heiko Voigt
2011-01-30 9:44 ` Julian Ibarz
2011-02-03 4:31 ` Julian Ibarz
2011-02-06 18:51 ` Heiko Voigt
2011-02-09 19:36 ` Heiko Voigt
2011-02-12 20:32 ` Julian Ibarz
2011-02-13 13:30 ` Heiko Voigt
2011-02-13 18:59 ` Julian Ibarz
2011-02-14 21:13 ` Heiko Voigt
2011-02-20 1:15 ` Julian Ibarz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v7hdrl7nw.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=julian.ibarz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).