From: Stefan Beller <sbeller@google.com>
To: Remi Galan Alfonso <remi.galan-alfonso@ensimag.grenoble-inp.fr>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Jens Lehmann <Jens.Lehmann@web.de>
Subject: Re: [PATCH 2/2] submodule update: learn `--[no-]recommend-shallow` option
Date: Thu, 26 May 2016 10:29:07 -0700 [thread overview]
Message-ID: <CAGZ79kY1yWp0r1XzRUVxnFC3jee1w3LtXUkx5NUjNoBWbbXMhg@mail.gmail.com> (raw)
In-Reply-To: <135840520.44198.1464253655936.JavaMail.zimbra@ensimag.grenoble-inp.fr>
On Thu, May 26, 2016 at 2:07 AM, Remi Galan Alfonso
<remi.galan-alfonso@ensimag.grenoble-inp.fr> wrote:
> You forgot to update from recommend-depth to recommend-shallow
>
> Stefan Beller <sbeller@google.com> writes:
>> [...]
>> 'git submodule' [--quiet] init [--] [<path>...]
>> 'git submodule' [--quiet] deinit [-f|--force] (--all|[--] <path>...)
>> 'git submodule' [--quiet] update [--init] [--remote] [-N|--no-fetch]
>> - [-f|--force] [--rebase|--merge] [--reference <repository>]
>> - [--depth <depth>] [--recursive] [--jobs <n>] [--] [<path>...]
>> + [--[no-]recommended-depth] [-f|--force] [--rebase|--merge]
>
> Here...
>
>> +--[no-]recommended-depth::
>> + This option is only valid for the update command.
>> + The initial clone of a submodule will use the recommended
>> + `submodule.<name>.depth` as provided by the .gitmodules file.
>> +
>
> ... and here.
>
> Thanks,
> Rémi
Thanks for the review,
these will be fixed in a reroll.
Thanks,
Stefan
next prev parent reply other threads:[~2016-05-26 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 0:06 [PATCHv2 0/2] Submodule shallow recommendation [WAS: Submodules: have a depth field in the .gitmodules file] Stefan Beller
2016-05-26 0:06 ` [PATCH 1/2] submodule-config: keep shallow recommendation around Stefan Beller
2016-05-26 9:02 ` Remi Galan Alfonso
2016-05-26 17:22 ` Stefan Beller
2016-05-26 0:06 ` [PATCH 2/2] submodule update: learn `--[no-]recommend-shallow` option Stefan Beller
2016-05-26 9:07 ` Remi Galan Alfonso
2016-05-26 17:29 ` Stefan Beller [this message]
2016-05-26 18:13 ` [PATCHv2 0/2] Submodule shallow recommendation [WAS: Submodules: have a depth field in the .gitmodules file] Junio C Hamano
2016-05-26 18:54 ` Stefan Beller
2016-05-26 19:16 ` Junio C Hamano
2016-05-26 21:20 ` Stefan Beller
-- strict thread matches above, loose matches on Subject: below --
2016-05-26 21:59 [PATCHv3 " Stefan Beller
2016-05-26 21:59 ` [PATCH 2/2] submodule update: learn `--[no-]recommend-shallow` option Stefan Beller
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=CAGZ79kY1yWp0r1XzRUVxnFC3jee1w3LtXUkx5NUjNoBWbbXMhg@mail.gmail.com \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=remi.galan-alfonso@ensimag.grenoble-inp.fr \
/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).