From: Junio C Hamano <gitster@pobox.com>
To: Heiko Voigt <hvoigt@hvoigt.net>
Cc: git@vger.kernel.org, Jens Lehmann <jens.lehmann@web.de>
Subject: Re: [PATCH 0/2] Add an update=none option for 'loose' submodules
Date: Thu, 11 Aug 2011 11:28:31 -0700 [thread overview]
Message-ID: <7v8vqzreeo.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <cover.1312923673.git.hvoigt@hvoigt.net> (Heiko Voigt's message of "Thu, 11 Aug 2011 19:51:44 +0200")
Heiko Voigt <hvoigt@hvoigt.net> writes:
> If a submodule is used to seperate some bigger parts of a project into
> an optional directory it is helpful to not clone/update them by default.
Sorry if I am slow, but I do not get this.
I thought unless you say "submodule init" once, a submodule you are not
interested in should not be cloned nor updated at all. If that is not the
case, isn't it a bug to be fixed without a new configuration variable that
fixes it only when it is set?
> We have been talking about loose submodules for some time:
Also before introducing a new terminology "loose submodule", please define
it somewhere. It feels confusing to me that a normal submodule, which
shouldn't be auto-cloned nor auto-updated without "submodule init", needs
to be called by a name other than simply a "submodule" but with an
adjuctive "loose submodule".
next prev parent reply other threads:[~2011-08-11 18:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 17:51 [PATCH 0/2] Add an update=none option for 'loose' submodules Heiko Voigt
2011-08-11 17:51 ` [PATCH 1/2] submodule: move update configuration variable further up Heiko Voigt
2011-08-11 17:51 ` [PATCH 2/2] add update 'none' flag to disable update of submodule by default Heiko Voigt
2011-08-11 18:28 ` Junio C Hamano [this message]
2011-08-11 20:00 ` [PATCH 0/2] Add an update=none option for 'loose' submodules Heiko Voigt
2011-08-15 20:37 ` Junio C Hamano
2011-08-22 20:00 ` Heiko Voigt
2011-08-22 22:42 ` Junio C Hamano
2011-08-23 19:43 ` Heiko Voigt
2011-08-23 20:18 ` Jens Lehmann
2011-08-23 21:46 ` Junio C Hamano
2011-08-24 19:30 ` Heiko Voigt
2011-08-26 6:27 ` Junio C Hamano
2011-08-26 16:14 ` Jens Lehmann
2011-08-24 20:38 ` Heiko Voigt
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=7v8vqzreeo.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=jens.lehmann@web.de \
/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).