From: Jens Lehmann <Jens.Lehmann@web.de>
To: Phil Hord <phil.hord@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Heiko Voigt <hvoigt@hvoigt.net>,
Fredrik Gustafsson <iveqy@iveqy.com>,
git@vger.kernel.org
Subject: Re: [PATCH v4 2/2] push: teach --recurse-submodules the on-demand option
Date: Mon, 12 Dec 2011 23:29:49 +0100 [thread overview]
Message-ID: <4EE6805D.7020708@web.de> (raw)
In-Reply-To: <CABURp0okOmsk4JV9Ku5pHJb5vT-kr_fmweNNBKZ_OoRyfZan=Q@mail.gmail.com>
Am 12.12.2011 22:16, schrieb Phil Hord:
> On Tue, Oct 18, 2011 at 4:58 PM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
>> Am 18.10.2011 00:33, schrieb Junio C Hamano:
>>> We could even declare that the gitlink for such a
>>> submodule should record 0{40} SHA-1 in the superproject, but I do not
>>> think that is necessary.
>>
>> Me neither, e.g. the SHA-1 which was the submodules HEAD when it was added
>> should do nicely. And that would avoid referencing a non-existing commit
>> in case you later want to turn a floating submodule into an exact one.
>
>
> I'm sorry I missed this comment before.
>
> I hope we can allow storing the actual gitlink in the superproject for
> each commit even when we're using floating submodules.
I think you misread my statement, I was just talking about the initial
commit containing the newly added submodule, not any subsequent ones.
Floating makes differences between the original SHA-1 and the current
tip of the branch invisible, so there is nothing to commit.
> I thought-experimented with this a bit last year and came to the
> conclusion that I should be able to 'float' to tips (developer
> convenience) and also to store the SHA-1 of each gitlink through
> history (automated maybe; as-needed).
Which means that after "git submodule update" floated a submodule branch
further, you would have to commit that in the superproject.
> The problem with "float-only" is that it loses history so, for
> example, git-bisect doesn't work.
Yep. And different developers can have the same superproject commit
checked out but their submodules can be quite different.
> The problem with "float + gitlinks", of course, is that it looks like
> "not floating" to the developers (git-status is dirty unless
> overridden, etc.)
Yeah. But what if each "git submodule update" would update the tip of
the submodule branch and add that to the superproject? You could follow
a tip but still produce reproducible trees.
next prev parent reply other threads:[~2011-12-12 22:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 22:08 [PATCH v4 0/2] push: submodule support Fredrik Gustafsson
2011-08-19 22:08 ` [PATCH v4 1/2] push: Don't push a repository with unpushed submodules Fredrik Gustafsson
2011-08-19 23:26 ` Junio C Hamano
2011-08-20 6:32 ` Junio C Hamano
2011-08-21 6:48 ` Junio C Hamano
2011-08-22 19:47 ` Heiko Voigt
2011-08-22 22:22 ` Junio C Hamano
2011-08-23 19:45 ` Heiko Voigt
2011-08-24 21:14 ` [WIP PATCH] revision-walking: allow iterating revisions multiple times Heiko Voigt
2011-08-24 21:44 ` Junio C Hamano
2011-08-20 6:34 ` [PATCH 2/2] demonstrate format-callback used in combined diff Junio C Hamano
2011-08-21 21:55 ` Fredrik Gustafsson
2011-08-19 22:08 ` [PATCH v4 2/2] push: teach --recurse-submodules the on-demand option Fredrik Gustafsson
2011-09-02 18:21 ` Junio C Hamano
[not found] ` <20111017190749.GA3126@sandbox-rc>
2011-10-17 22:33 ` Junio C Hamano
2011-10-18 20:58 ` Jens Lehmann
2011-12-12 21:16 ` Phil Hord
2011-12-12 22:29 ` Jens Lehmann [this message]
2011-12-12 23:50 ` Phil Hord
2011-12-13 8:48 ` Jens Lehmann
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=4EE6805D.7020708@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=iveqy@iveqy.com \
--cc=phil.hord@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 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.