From: Junio C Hamano <gitster@pobox.com>
To: Stefan Monov <logixoul@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Making it possible to do “git push origin” instead of “git push origin <branch>”, without having to one-time prepare each branch for it
Date: Thu, 22 Dec 2016 13:41:49 -0800 [thread overview]
Message-ID: <xmqq7f6rfxpe.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAJtFkWtjowyGaFfsCVd-HAZM2-3e0=CkkyYfxne8KRdYq5kJ9g@mail.gmail.com> (Stefan Monov's message of "Thu, 22 Dec 2016 23:14:31 +0200")
Stefan Monov <logixoul@gmail.com> writes:
> I'd like to use just:
>
> git push
>
> or at most:
>
> git push origin
>
> rather than having to first check which is the active branch with `git
> branch --list`, then type:
>
> git push origin <branch>
Perhaps you are a target audience of
$ git config push.default current
then?
next prev parent reply other threads:[~2016-12-22 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 21:14 Making it possible to do “git push origin” instead of “git push origin <branch>”, without having to one-time prepare each branch for it Stefan Monov
2016-12-22 21:18 ` Stefan Monov
2016-12-22 21:41 ` Junio C Hamano [this message]
2016-12-22 21:46 ` Jacob Keller
2016-12-27 17:47 ` Stefan Monov
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=xmqq7f6rfxpe.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=logixoul@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