From: Jens Lehmann <Jens.Lehmann@web.de>
To: Git Mailing List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Heiko Voigt <hvoigt@hvoigt.net>,
"W. Trevor King" <wking@tremily.us>
Subject: [WIP/PATCH 0/9] v2 submodule recursive checkout]
Date: Mon, 03 Feb 2014 20:47:42 +0100 [thread overview]
Message-ID: <52EFF25E.6080306@web.de> (raw)
In-Reply-To: <xmqqvbxvekwv.fsf@gitster.dls.corp.google.com>
Am 07.01.2014 18:55, schrieb Junio C Hamano:
> Jens Lehmann <Jens.Lehmann@web.de> writes:
>
>> Am 06.01.2014 23:36, schrieb Junio C Hamano:
>>> * jl/submodule-recursive-checkout (2013-12-26) 5 commits
>>> - Teach checkout to recursively checkout submodules
>>> - submodule: teach unpack_trees() to update submodules
>>> - submodule: teach unpack_trees() to repopulate submodules
>>> - submodule: teach unpack_trees() to remove submodule contents
>>> - submodule: prepare for recursive checkout of submodules
>>>
>>> What is the doneness of this one???
>>
>> It's still work in progress. Currently I'm working on a test
>> framework so we can reuse recursive submodule checkout tests
>> instead of rewriting them for every command that learns the
>> --recurse-submodule option. Will reroll this series as soon
>> as I have something presentable.
>
> Thanks.
Ok, time for another round. This is still WIP/RFC and not
ready to be merged yet, but I believe this round makes it a
bit more clear where this is heading.
Changes to the first version are:
- Reordered the commits according to Jonathan's proposal
(this currently makes the checkout tests fail until the
last commit completes the functionality; this will be
fixed when the test framework is added)
- Fixed calling parse_fetch_recurse_submodules_arg() where
parse_update_recurse_submodules_arg() must be used.
- Moved the documentation of the --[no-]recurse-submodule
option into an include file so different commands can
reuse it.
- Added the --[no-]recurse-submodule option to bisect, merge
and reset too.
Tests, documentation and commit messages are not complete yet,
I'll work on them in the next rounds. The wiki page in my Github
repository will describe the current status of this series:
https://github.com/jlehmann/git-submod-enhancements/wiki/Recursive-submodule-checkout
Jens Lehmann (9):
submodule: prepare for recursive checkout of submodules
Teach reset the --[no-]recurse-submodules option
Teach checkout the --[no-]recurse-submodules option
Teach merge the --[no-]recurse-submodules option
Teach bisect--helper the --[no-]recurse-submodules option
Teach bisect the --[no-]recurse-submodules option
submodule: teach unpack_trees() to remove submodule contents
submodule: teach unpack_trees() to repopulate submodules
submodule: teach unpack_trees() to update submodules
Documentation/git-bisect.txt | 5 +
Documentation/git-checkout.txt | 2 +
Documentation/git-merge.txt | 2 +
Documentation/git-reset.txt | 4 +
Documentation/recurse-submodules-update.txt | 8 +
bisect.c | 33 ++--
bisect.h | 3 +-
builtin/bisect--helper.c | 9 +-
builtin/checkout.c | 14 ++
builtin/merge.c | 14 ++
builtin/reset.c | 14 ++
entry.c | 19 ++-
git-bisect.sh | 29 +++-
submodule.c | 238 +++++++++++++++++++++++++++-
submodule.h | 12 ++
t/t2013-checkout-submodule.sh | 215 ++++++++++++++++++++++++-
unpack-trees.c | 95 +++++++++--
unpack-trees.h | 1 +
wrapper.c | 3 +
19 files changed, 676 insertions(+), 44 deletions(-)
create mode 100644 Documentation/recurse-submodules-update.txt
--
1.9.rc0.28.ge3363ff
next prev parent reply other threads:[~2014-02-03 19:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 22:36 What's cooking in git.git (Jan 2014, #01; Mon, 6) Junio C Hamano
2014-01-06 23:16 ` Francesco Pretto
2014-01-06 23:32 ` Junio C Hamano
2014-01-06 23:45 ` Francesco Pretto
2014-01-07 17:49 ` Jens Lehmann
[not found] ` <xmqqvbxvekwv.fsf@gitster.dls.corp.google.com>
2014-02-03 19:47 ` Jens Lehmann [this message]
2014-02-03 19:48 ` [WIP/PATCH 1/9] submodule: prepare for recursive checkout of submodules Jens Lehmann
2014-02-03 22:23 ` Junio C Hamano
2014-02-07 21:06 ` Jens Lehmann
2014-02-04 0:01 ` Jonathan Nieder
2014-02-07 21:01 ` Jens Lehmann
2014-02-03 19:49 ` [WIP/PATCH 2/9] Teach reset the --[no-]recurse-submodules option Jens Lehmann
2014-02-03 22:40 ` Junio C Hamano
2014-02-07 21:09 ` Jens Lehmann
2014-02-03 19:50 ` [WIP/PATCH 3/9] Teach checkout " Jens Lehmann
2014-02-03 22:56 ` Junio C Hamano
2014-02-07 21:12 ` Jens Lehmann
2014-02-03 19:50 ` [WIP/PATCH 4/9] Teach merge " Jens Lehmann
2014-02-03 23:01 ` Junio C Hamano
2014-02-07 21:23 ` Jens Lehmann
2014-02-07 22:00 ` Junio C Hamano
2014-02-07 22:08 ` W. Trevor King
2014-02-03 19:51 ` [WIP/PATCH 5/9] Teach bisect--helper " Jens Lehmann
2014-02-03 19:51 ` [WIP/PATCH 6/9] Teach bisect " Jens Lehmann
2014-02-03 20:04 ` W. Trevor King
2014-02-03 20:22 ` Jens Lehmann
2014-02-03 19:52 ` [WIP/PATCH 7/9] submodule: teach unpack_trees() to remove submodule contents Jens Lehmann
2014-02-03 20:10 ` W. Trevor King
2014-02-07 21:24 ` Jens Lehmann
2014-02-03 19:53 ` [WIP/PATCH 8/9] submodule: teach unpack_trees() to repopulate submodules Jens Lehmann
2014-02-03 19:54 ` [WIP/PATCH 9/9] submodule: teach unpack_trees() to update submodules Jens Lehmann
2014-02-03 20:19 ` W. Trevor King
2014-02-07 21:25 ` Jens Lehmann
2014-02-04 0:11 ` Duy Nguyen
2014-02-07 21:32 ` 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=52EFF25E.6080306@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=jrnieder@gmail.com \
--cc=wking@tremily.us \
/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).