From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org
Cc: Jens.Lehmann@web.de, gitster@pobox.com, jrnieder@gmail.com,
Stefan Beller <sbeller@google.com>
Subject: [PATCH 0/3] Submodules: have a depth field in the .gitmodules file
Date: Wed, 25 May 2016 15:00:03 -0700 [thread overview]
Message-ID: <20160525220006.27138-1-sbeller@google.com> (raw)
Sometimes the history of a submodule is not considered important by
the projects upstream. To make it easier for downstream users, allow
a field 'submodule.<name>.depth' in .gitmodules, which can be used
to indicate the recommended depth.
Stefan Beller (3):
submodule update: make use of the existing fetch_in_submodule function
submodule-config: keep `depth` around
submodule update: learn `--recommended-depth` option
Documentation/git-submodule.txt | 10 ++++++++--
builtin/submodule--helper.c | 8 +++++++-
git-submodule.sh | 11 +++++++++--
submodule-config.c | 16 ++++++++++++++++
submodule-config.h | 1 +
t/t5614-clone-submodules.sh | 34 ++++++++++++++++++++++++++++++++++
6 files changed, 75 insertions(+), 5 deletions(-)
--
2.9.0.rc0.3.g892bdd0.dirty
base-commit: 3a0f269e7c82aa3a87323cb7ae04ac5f129f036b
next reply other threads:[~2016-05-25 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 22:00 Stefan Beller [this message]
2016-05-25 22:00 ` [PATCH 1/3] submodule update: make use of the existing fetch_in_submodule function Stefan Beller
2016-05-25 22:41 ` Junio C Hamano
2016-05-25 22:45 ` Stefan Beller
2016-05-25 22:00 ` [PATCH 2/3] submodule-config: keep `depth` around Stefan Beller
2016-05-25 22:00 ` [PATCH 3/3] submodule update: learn `--recommended-depth` option Stefan Beller
2016-05-25 22:38 ` [PATCH 0/3] Submodules: have a depth field in the .gitmodules file Junio C Hamano
2016-05-25 22:44 ` Stefan Beller
2020-08-02 15:14 ` medoo
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=20160525220006.27138-1-sbeller@google.com \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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.