From: Mathias Kunter <mathiaskunter@gmail.com>
To: git@vger.kernel.org
Subject: git push doesn't use local branch name as default
Date: Fri, 28 May 2021 08:29:49 +0200 [thread overview]
Message-ID: <fcf30899-8e64-5417-f478-14d6aca72544@gmail.com> (raw)
In-Reply-To: <3b9bc214-a30a-ba49-af96-7eeaf37b7bbd@gmail.com>
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", and thus, according to the doc, `simple` should actually work
like `current` in this case. Am I wrong here?
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.
Cheers
Mathias Kunter
Am 27.05.21 um 21:51 schrieb Felipe Contreras:
> Mathias Kunter wrote:
>> Hi all,
>>
>> at https://git-scm.com/docs/git-push#_description it says:
>>
>>> When neither the command-line nor the configuration specify what to
>>> push, the default behavior is used, which corresponds to the simple
>>> value for push.default: the current branch is pushed to the
>>> corresponding upstream branch, but as a safety measure, the push is
>>> aborted if the upstream branch does not have the same name as the local
>>> one.
>>
>> However, on a branch which does *not* have an upstream branch
>> configured, the command
>>
>>> git push <remote_name>
>>
>> doesn't use the local branch name as default,
>
> Yes it does, but only on the src side of the refspec. Something like:
>
> git push <remote_name> <branch_name>:
>
> (invalid refspec)
>
> Note the remote side is missing, so git doesn't know where to push to.
>
>> Note that it *does* work if the remote branch name is explicitly specified:
>>
>>> git push <remote_name> <branch_name>
>
> In that case git assumes you mean <branch_name>:<branch_name>.
>
> Sounds like you want to change the default to `push.default=current`.
>
> Cheers.
>
next parent reply other threads:[~2021-05-28 6:29 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 ` Mathias Kunter [this message]
2021-05-28 7:00 ` git push doesn't use local branch name as default 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
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
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=fcf30899-8e64-5417-f478-14d6aca72544@gmail.com \
--to=mathiaskunter@gmail.com \
--cc=git@vger.kernel.org \
/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).