From: Felipe Contreras <felipe.contreras@gmail.com>
To: Mathias Kunter <mathiaskunter@gmail.com>, git@vger.kernel.org
Subject: RE: git push doesn't use local branch name as default
Date: Fri, 28 May 2021 12:10:16 -0500 [thread overview]
Message-ID: <60b123f8b0586_5190820868@natae.notmuch> (raw)
In-Reply-To: <fcf30899-8e64-5417-f478-14d6aca72544@gmail.com>
Mathias Kunter wrote:
> Felipe,
>
> thanks for your reply.
>
> > Sounds like you want to change the default to `push.default=current`.
>
> Yes, but shouldn't `simple` pushing also work? The documentation says
> about `push.default=simple`:
>
> > When pushing to a remote that is different from the remote you normally
> > pull from, work as `current`.
>
> If there is no upstream, then there also is no "remote I normally pull
> from",
If there's no upstream the remote is "origin".
> and thus, according to the doc, `simple` should actually work
> like `current` in this case. Am I wrong here?
Only if you are not pushing to "origin".
> If `simple` pushing is used, it doesn't seem to make sense for me to
> fallback to `current` on branches which *do* have an upstream, but to
> error out on branches which do *not* have an upstream.
That is not the criteria. It depends whether or not you are in a
triangular workflow [1].
If you pull from kernel.org, but push to github.com, then you are in a
triangular workflow and the name of the branch is not checked.
The oposite is a centralized workflow, where you pull and push to the
same repository, then git adds an extra check.
If you don't want to set `push.default`, you can alternatively rename
your remote to something other than "origin", then your branches with no
upstram truly would have nowhere to fetch from.
But then `git fetch` without arguments will not do anything.
Cheers.
[1] https://felipec.wordpress.com/2014/05/11/git-triangular-workflows/
--
Felipe Contreras
next prev parent reply other threads:[~2021-05-28 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3b9bc214-a30a-ba49-af96-7eeaf37b7bbd@gmail.com>
2021-05-28 6:29 ` git push doesn't use local branch name as default Mathias Kunter
2021-05-28 7:00 ` Elijah Newren
2021-05-28 7:44 ` Mathias Kunter
2021-05-28 8:51 ` Mathias Kunter
2021-05-28 21:12 ` git push default doesn't make sense Felipe Contreras
2021-05-30 16:28 ` Mathias Kunter
2021-05-30 16:32 ` Felipe Contreras
2021-05-28 17:52 ` git push doesn't use local branch name as default Felipe Contreras
2021-05-28 17:22 ` Felipe Contreras
2021-05-28 17:44 ` Elijah Newren
2021-05-28 18:58 ` Felipe Contreras
2021-05-28 17:10 ` Felipe Contreras [this message]
2021-05-27 17:06 Mathias Kunter
2021-05-27 19:51 ` Felipe Contreras
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=60b123f8b0586_5190820868@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=mathiaskunter@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.
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 NNTP newsgroup(s).