From: Robert Dailey <rcdailey.lists@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git <git@vger.kernel.org>
Subject: Re: Using push.default with push.remote.push
Date: Wed, 11 Mar 2020 11:56:05 -0500 [thread overview]
Message-ID: <CAHd499AGQ5k7ON+YY84b6LY1sh9MOw8fsrE2shOibujX1iKeiQ@mail.gmail.com> (raw)
In-Reply-To: <20200311162517.GA27893@coredump.intra.peff.net>
On Wed, Mar 11, 2020 at 11:25 AM Jeff King <peff@peff.net> wrote:
> > The current behavior seems to be working as designed, but not as
> > desired. The first push command pushes *all* branches under
> > `refs/heads/*`, instead of just the current branch as it normally
> > would via `push.default` setting. It sort of feels like if a resolved,
> > explicitly defined `push.<remote>.push` config is found *and* it
> > includes wildcards, the `push.default` setting should still be
> > respected.
>
> Then when would remote.*.push with a wildcard ever do anything?
Maybe this is where a potential disconnect is, but I've always viewed
the wildcard refspec as a mapping, rather than an all-inclusive "Push
all the things". In other words, I view it as more of a structural
guide than a behavioral one. I recognize I probably have this wrong,
but it probably speaks to how some users view it, or at least, some
valid use cases to have more of a structural mechanism to map branches
to remote repositories, with `git push --all` being a supplement to
say "Push all branches using this mapping".
next prev parent reply other threads:[~2020-03-11 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 15:41 Using push.default with push.remote.push Robert Dailey
2020-03-11 15:43 ` Robert Dailey
2020-03-11 16:25 ` Jeff King
2020-03-11 16:56 ` Robert Dailey [this message]
2020-03-11 17:01 ` Robert Dailey
2020-03-11 19:10 ` Jeff King
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=CAHd499AGQ5k7ON+YY84b6LY1sh9MOw8fsrE2shOibujX1iKeiQ@mail.gmail.com \
--to=rcdailey.lists@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).