From: Julian Ibarz <julian.ibarz@gmail.com>
To: Junio C Hamano <gitster@pobox.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 15:45:38 -0500 [thread overview]
Message-ID: <AANLkTik8VrhbBSLwRq9gd39hofnmifk15zSqXVTsSzAp@mail.gmail.com> (raw)
In-Reply-To: <7v7hdrl7nw.fsf@alter.siamese.dyndns.org>
On Wed, Jan 26, 2011 at 3:41 PM, Junio C Hamano <gitster@pobox.com> wrote:
> 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???
>
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).
next prev parent reply other threads:[~2011-01-26 20:45 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
2011-01-26 20:45 ` Julian Ibarz [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTik8VrhbBSLwRq9gd39hofnmifk15zSqXVTsSzAp@mail.gmail.com \
--to=julian.ibarz@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.