From: "W. Trevor King" <wking@tremily.us>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Heiko Voigt <hvoigt@hvoigt.net>,
Chris Packham <judge.packham@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, mara.kim@vanderbilt.edu,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: Re: [RFC PATCH] clone: add clone.recursesubmodules config option
Date: Mon, 9 Jun 2014 16:27:25 -0700 [thread overview]
Message-ID: <20140609232725.GA9047@odin.tremily.us> (raw)
In-Reply-To: <5395B3D3.9060501@web.de>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
On Mon, Jun 09, 2014 at 03:17:07PM +0200, Jens Lehmann wrote:
> And by the way: wouldn't it make more sense to tell the user /what/
> we do automatically? So maybe 'submodule.autoupdate' is a better
> name for the new switch?
Or autocheckout? No need to preserve submodule-specific jargon when
we have a perfectly acceptable word for this in the core interface ;).
Cheers,
Trevor
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-06-09 23:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 18:11 Paper cut bug: Why isn't "git clone xxxx" recursive by default? Mara Kim
2014-06-03 19:52 ` Junio C Hamano
2014-06-03 21:05 ` Junio C Hamano
2014-06-03 22:24 ` Mara Kim
2014-06-04 9:30 ` [RFC PATCH] clone: add clone.recursesubmodules config option Chris Packham
2014-06-04 17:24 ` Junio C Hamano
2014-06-04 19:06 ` Jens Lehmann
2014-06-05 18:18 ` Junio C Hamano
2014-06-05 18:43 ` W. Trevor King
2014-06-06 5:26 ` Heiko Voigt
2017-08-02 18:11 ` Jeremy Morton
2017-08-02 20:34 ` Stefan Beller
2014-06-04 19:42 ` Heiko Voigt
2014-06-05 7:48 ` Chris Packham
2014-06-06 5:54 ` Heiko Voigt
2014-06-06 16:35 ` Junio C Hamano
2014-06-09 13:17 ` Jens Lehmann
2014-06-09 23:27 ` W. Trevor King [this message]
2016-10-03 15:36 ` Jeremy Morton
2016-10-03 17:18 ` Stefan Beller
2016-10-04 11:41 ` 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
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=20140609232725.GA9047@odin.tremily.us \
--to=wking@tremily.us \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=jrnieder@gmail.com \
--cc=judge.packham@gmail.com \
--cc=mara.kim@vanderbilt.edu \
/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).