From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Tan <jonathantanmy@google.com>
Cc: Stefan Beller <sbeller@google.com>, git@vger.kernel.org
Subject: Re: [RFD] Long term plan with submodule refs?
Date: Thu, 09 Nov 2017 14:47:10 +0900 [thread overview]
Message-ID: <xmqq7ev0j95t.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171108172945.33c42a0e91b4ac494217b788@google.com> (Jonathan Tan's message of "Wed, 8 Nov 2017 17:29:45 -0800")
Jonathan Tan <jonathantanmy@google.com> writes:
> What if, in the submodule, we have a new ref backend that mirrors the
> superproject? When initializing the submodule, its original refs are not
> cloned at all, but instead virtual refs are used.
> ...
> These rules seem straightforward to me (although I have been working
> with Git for a while, so perhaps I'm not the best judge), and I think
> leads to a good workflow, as discussed below.
Indeed this is intriguing.
> The above rules allow the following workflow:
> - "checkout --recurse-submodules" the branch you want on the
> superproject
> - make whatever changes you want in each submodule
> - commit each individual submodule (which updates the index of the
> superproject), then commit the superproject (we can introduce a
> commit --recurse-submodules to make this more convenient)
The "recurse" option would also give users an extra atomicity, and
would not be merely for convenience; when a user wants to treat a
superproject and its two submodules as if the combined whole were a
single repository, there shouldn't be two separate commits in the
history of the superproject only because two submodules made one
commit each to work on a single theme that spans all of them.
next prev parent reply other threads:[~2017-11-09 5:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 19:55 [RFC PATCH 0/4] git-status reports relation to superproject Stefan Beller
2017-11-08 19:55 ` [PATCH 1/4] remote, revision: factor out exclusive counting between two commits Stefan Beller
2017-11-08 19:55 ` [PATCH 2/4] submodule.c: factor start_ls_files_dot_dot out of get_superproject_working_tree Stefan Beller
2017-11-08 19:55 ` [PATCH 3/4] submodule.c: get superprojects gitlink value Stefan Beller
2017-11-08 19:55 ` [PATCH 4/4] git-status: report reference to superproject Stefan Beller
2017-11-08 22:36 ` [RFC PATCH 0/4] git-status reports relation " Jonathan Tan
2017-11-09 0:10 ` [RFD] Long term plan with submodule refs? Stefan Beller
2017-11-09 1:29 ` Jonathan Tan
2017-11-09 5:47 ` Junio C Hamano [this message]
2017-11-09 5:08 ` Junio C Hamano
2017-11-09 19:57 ` Stefan Beller
2017-11-09 6:54 ` Jacob Keller
2017-11-09 20:16 ` Stefan Beller
2017-11-10 3:37 ` Jacob Keller
2017-11-10 20:01 ` Stefan Beller
2017-11-11 5:25 ` Jacob Keller
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=xmqq7ev0j95t.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=sbeller@google.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).