From: Heiko Voigt <hvoigt@hvoigt.net>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Junio C Hamano <gitster@pobox.com>,
henri GEIST <henri.geist@flying-robots.com>,
Alexei Sholik <alcosholik@gmail.com>,
git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: tracking submodules out of main directory.
Date: Wed, 3 Aug 2011 23:45:58 +0200 [thread overview]
Message-ID: <20110803214530.GA34347@book.hvoigt.net> (raw)
In-Reply-To: <4E399C62.30604@web.de>
Hi,
On Wed, Aug 03, 2011 at 09:07:14PM +0200, Jens Lehmann wrote:
> Am 03.08.2011 19:11, schrieb Junio C Hamano:
> But the superproject is still the place to say: I know these versions of
> all submodules work together, so I commit their gitlinks here. But this
> scheme enables submodules to give hints to help the superproject's user.
>
> > I also suspect that allowing each submodule to know and demand specific
> > versions of other submodules will lead to inconsistencies. Which version
> > of submodule C would you demand to have when submodule A wants version C0
> > and submodule B wants version C1 of it?
>
> Right, in the discussion so far it seemed like henri seems to be the only
> user who is wanting an exact match, and he says he needs to see these
> inconsistencies. But I think he can modify the "version xxx or newer" to
> his needs without imposing these inconsistencies on users (like me) who
> don't want to see them.
And I imagine if a submodule has such hints we could add a command say
git submodule resolve-dependencies
which could resolve such "I need a version newer than" hints given by a
submodule to help the user to update a submodule in the superproject.
Disclaimer: I think we need to think about all the implications such a
scheme introduces very carefully. The picture is still a bit blurry for
me.
Cheers Heiko
next prev parent reply other threads:[~2011-08-03 21:46 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 13:07 tracking submodules out of main directory henri GEIST
2011-06-27 16:51 ` Junio C Hamano
2011-06-27 18:14 ` Jens Lehmann
2011-06-27 18:52 ` henri GEIST
2011-06-27 18:56 ` Jens Lehmann
2011-06-27 21:18 ` henri GEIST
2011-06-27 19:05 ` Junio C Hamano
2011-06-27 19:40 ` Jens Lehmann
2011-06-27 21:57 ` henri GEIST
2011-06-28 7:25 ` Jens Lehmann
2011-06-28 11:55 ` henri GEIST
2011-06-27 21:51 ` henri GEIST
2011-06-28 7:20 ` Jens Lehmann
2011-06-28 7:37 ` Jens Lehmann
2011-06-28 11:52 ` henri GEIST
2011-06-28 10:05 ` Alexei Sholik
2011-06-28 17:00 ` Jens Lehmann
2011-07-27 18:49 ` henri GEIST
2011-07-28 8:57 ` henri GEIST
2011-07-28 16:48 ` Jens Lehmann
2011-07-29 9:39 ` henri GEIST
2011-07-30 14:16 ` Jens Lehmann
2011-07-30 21:55 ` henri GEIST
2011-08-01 19:39 ` Jens Lehmann
2011-08-02 12:19 ` henri GEIST
2011-08-02 18:42 ` Jens Lehmann
2011-08-03 6:25 ` Heiko Voigt
2011-08-03 12:26 ` henri GEIST
2011-08-03 17:11 ` Junio C Hamano
2011-08-03 19:07 ` Jens Lehmann
2011-08-03 19:41 ` Junio C Hamano
2011-08-03 21:30 ` Jens Lehmann
2011-08-03 22:29 ` henri GEIST
2011-08-04 17:45 ` Jens Lehmann
2011-08-05 0:29 ` henri GEIST
2011-08-04 20:05 ` Heiko Voigt
2011-08-05 2:19 ` henri GEIST
2011-08-03 21:45 ` Heiko Voigt [this message]
2011-08-03 22:41 ` henri GEIST
2011-08-03 21:49 ` henri GEIST
2011-08-03 21:04 ` henri GEIST
2011-08-01 22:12 ` Heiko Voigt
2011-08-02 12:58 ` henri GEIST
[not found] ` <CAJsNXT=93FHjbi42JKA3Pg7PGXs0kEONJ5AC5SSPpa5RSVqB=A@mail.gmail.com>
2011-08-03 9:07 ` henri GEIST
2011-06-27 18:40 ` henri GEIST
2011-06-27 19:02 ` Jens Lehmann
2011-06-27 21:45 ` henri GEIST
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=20110803214530.GA34347@book.hvoigt.net \
--to=hvoigt@hvoigt.net \
--cc=Jens.Lehmann@web.de \
--cc=alcosholik@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=henri.geist@flying-robots.com \
--cc=srabbelier@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.
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 NNTP newsgroup(s).