git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Brandon Williams <bmwill@google.com>
Cc: git@vger.kernel.org, jrnieder@gmail.com
Subject: Re: [PATCH v3 0/5] propagating push-options, remote and refspec
Date: Tue, 11 Apr 2017 00:44:36 -0700	[thread overview]
Message-ID: <xmqqr30zqtgb.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170405174719.1297-1-bmwill@google.com> (Brandon Williams's message of "Wed, 5 Apr 2017 10:47:14 -0700")

Brandon Williams <bmwill@google.com> writes:

> v3 builds upon v2 by adding 3 additional patches to add functionality to also
> propagate the remote and refspec down to children process's working to push
> submodules.  The remote and refspec will only be propagated if the provided
> remote is configured. A remote provided in the form of a URL will cause the
> remote and refspec to not be propagated down to the submodules and instead the
> default remote and refspec will be used, preserving existing functionality.
> Currently the only supported LHS of a refspec must exactly match a single ref
> in the submodule (e.g. a branch name).
>
> Patches [1/5] and [2/5] remain unchanged from v2.

2/5 seems to be a bit different in 5545 ll.156,+6, though.

>
> Brandon Williams (5):
>   push: unmark a local variable as static
>   push: propagate push-options with --recurse-submodules
>   remote: expose parse_push_refspec function
>   submodule--helper: add push-check subcommand
>   push: propagate remote and refspec with --recurse-submodules
>
>  builtin/push.c                 |  5 +--
>  builtin/submodule--helper.c    | 45 +++++++++++++++++++++++++
>  remote.c                       |  2 +-
>  remote.h                       |  1 +
>  submodule.c                    | 74 +++++++++++++++++++++++++++++++++++++++---
>  submodule.h                    |  5 ++-
>  t/t5531-deep-submodule-push.sh | 52 +++++++++++++++++++++++++++++
>  t/t5545-push-options.sh        | 40 +++++++++++++++++++++++
>  transport.c                    |  4 ++-
>  9 files changed, 219 insertions(+), 9 deletions(-)

  parent reply	other threads:[~2017-04-11  7:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 23:11 [PATCH] push: propagate push-options with --recurse-submodules Brandon Williams
2017-03-31 23:20 ` Jonathan Nieder
2017-03-31 23:26   ` Brandon Williams
2017-03-31 23:56 ` [PATCH v2 0/2] propagate push-options Brandon Williams
2017-03-31 23:56   ` [PATCH v2 1/2] push: unmark a local variable as static Brandon Williams
2017-04-01  0:11     ` Jonathan Nieder
2017-04-01  0:16       ` Brandon Williams
2017-03-31 23:56   ` [PATCH v2 2/2] push: propagate push-options with --recurse-submodules Brandon Williams
2017-04-01  0:19     ` Jonathan Nieder
2017-04-06  0:17       ` Jacob Keller
2017-04-06 17:39         ` Brandon Williams
2017-04-05 17:47   ` [PATCH v3 0/5] propagating push-options, remote and refspec Brandon Williams
2017-04-05 17:47     ` [PATCH v3 1/5] push: unmark a local variable as static Brandon Williams
2017-04-05 17:47     ` [PATCH v3 2/5] push: propagate push-options with --recurse-submodules Brandon Williams
2017-04-05 17:47     ` [PATCH v3 3/5] remote: expose parse_push_refspec function Brandon Williams
2017-04-05 17:47     ` [PATCH v3 4/5] submodule--helper: add push-check subcommand Brandon Williams
2017-04-05 17:47     ` [PATCH v3 5/5] push: propagate remote and refspec with --recurse-submodules Brandon Williams
2017-04-11  7:44     ` Junio C Hamano [this message]
2017-04-11 16:33       ` [PATCH v3 0/5] propagating push-options, remote and refspec Brandon Williams

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=xmqqr30zqtgb.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=bmwill@google.com \
    --cc=git@vger.kernel.org \
    --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.
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).