From: Junio C Hamano <gitster@pobox.com>
To: cornelius.weig@tngtech.com
Cc: git@vger.kernel.org, bmwill@google.com, sbeller@google.com
Subject: Re: [PATCH 1/2] doc: add doc for git-push --recurse-submodules=only
Date: Wed, 01 Feb 2017 15:16:45 -0800 [thread overview]
Message-ID: <xmqqinotmrhe.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170201230753.19462-1-cornelius.weig@tngtech.com> (cornelius weig's message of "Thu, 2 Feb 2017 00:07:52 +0100")
cornelius.weig@tngtech.com writes:
> From: Cornelius Weig <cornelius.weig@tngtech.com>
>
> Add documentation for the `--recurse-submodules=only` option of
> git-push. The feature was added in commit 225e8bf (add option to
> push only submodules).
>
> Signed-off-by: Cornelius Weig <cornelius.weig@tngtech.com>
> ---
>
> Notes:
> This feature is already in 'next' but was undocumented. Unless somebody reads
> the release notes, there is no way of knowing about it.
Good eyes; the topic bw/push-submodule-only is already in 'master'.
Looks good to me; Brandon?
>
> Documentation/git-push.txt | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
> index 8eefabd..1624a35 100644
> --- a/Documentation/git-push.txt
> +++ b/Documentation/git-push.txt
> @@ -272,7 +272,7 @@ origin +master` to force a push to the `master` branch). See the
> standard error stream is not directed to a terminal.
>
> --no-recurse-submodules::
> ---recurse-submodules=check|on-demand|no::
> +--recurse-submodules=check|on-demand|only|no::
> May be used to make sure all submodule commits used by the
> revisions to be pushed are available on a remote-tracking branch.
> If 'check' is used Git will verify that all submodule commits that
> @@ -280,11 +280,12 @@ origin +master` to force a push to the `master` branch). See the
> remote of the submodule. If any commits are missing the push will
> be aborted and exit with non-zero status. If 'on-demand' is used
> all submodules that changed in the revisions to be pushed will be
> - pushed. If on-demand was not able to push all necessary revisions
> - it will also be aborted and exit with non-zero status. A value of
> - 'no' or using `--no-recurse-submodules` can be used to override the
> - push.recurseSubmodules configuration variable when no submodule
> - recursion is required.
> + pushed. If on-demand was not able to push all necessary revisions it will
> + also be aborted and exit with non-zero status. If 'only' is used all
> + submodules will be recursively pushed while the superproject is left
> + unpushed. A value of 'no' or using `--no-recurse-submodules` can be used
> + to override the push.recurseSubmodules configuration variable when no
> + submodule recursion is required.
>
> --[no-]verify::
> Toggle the pre-push hook (see linkgit:githooks[5]). The
next prev parent reply other threads:[~2017-02-01 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 23:07 [PATCH 1/2] doc: add doc for git-push --recurse-submodules=only cornelius.weig
2017-02-01 23:07 ` [PATCH 2/2] completion: add completion for --recurse-submodules=only cornelius.weig
2017-02-02 9:30 ` Stefan Beller
2017-02-01 23:16 ` Junio C Hamano [this message]
[not found] ` <CAKoko1q=6agpGsABxy8rmm6sGFWx9gE_c1j44h4M=yJ3r4JJBQ@mail.gmail.com>
2017-02-02 9:32 ` Fwd: [PATCH 1/2] doc: add doc for git-push --recurse-submodules=only Brandon Williams
2017-02-04 12:05 ` Cornelius Weig
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=xmqqinotmrhe.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=bmwill@google.com \
--cc=cornelius.weig@tngtech.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.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.
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).