From: Casey Fitzpatrick <kcghost@gmail.com>
To: git@vger.kernel.org, sbeller@google.com, sunshine@sunshineco.com,
gitster@pobox.com
Cc: Casey Fitzpatrick <kcghost@gmail.com>
Subject: [PATCH v4 0/3] Add --progress and --dissociate to git submodule
Date: Thu, 3 May 2018 06:53:43 -0400 [thread overview]
Message-ID: <20180503105346.1758-1-kcghost@gmail.com> (raw)
These patches add --progress and --dissociate options to git submodule.
The --progress option existed beforehand, but only for the update command and
it was left undocumented.
Both add and update submodule commands supported --reference, but not its pair
option --dissociate which allows for independent clones rather than depending
on the reference.
This is a resubmission with comments from Stefan Beller, Eric Sunshine, and
Junio C Hamano addressed.
Casey Fitzpatrick (3):
submodule: clean up subsititions in script
submodule: add --progress option to add command
submodule: add --dissociate option to add/update commands
Documentation/git-submodule.txt | 17 ++++++++++++++++-
builtin/submodule--helper.c | 16 +++++++++++++---
git-submodule.sh | 21 ++++++++++++++++-----
t/t7400-submodule-basic.sh | 16 ++++++++++++++++
t/t7408-submodule-reference.sh | 17 +++++++++++++++++
5 files changed, 78 insertions(+), 9 deletions(-)
--
2.17.0.1.ge0414f29c.dirty
next reply other threads:[~2018-05-03 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 10:53 Casey Fitzpatrick [this message]
2018-05-03 10:53 ` [PATCH v4 1/3] submodule: clean up subsititions in script Casey Fitzpatrick
2018-05-03 10:53 ` [PATCH v4 2/3] submodule: add --progress option to add command Casey Fitzpatrick
2018-05-03 10:53 ` [PATCH v4 3/3] submodule: add --dissociate option to add/update commands Casey Fitzpatrick
2018-05-17 2:48 ` [PATCH v4 0/3] Add --progress and --dissociate to git submodule Junio C Hamano
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=20180503105346.1758-1-kcghost@gmail.com \
--to=kcghost@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.com \
--cc=sunshine@sunshineco.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.