git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Patryk Obara <dreamer.tan@gmail.com>
To: Cliff Schomburg <clisc@microsoft.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Simple shortcut for "git push --set-upstream origin newBranchName"
Date: Fri, 31 May 2019 17:05:24 +0200	[thread overview]
Message-ID: <ebc03b4e-daf8-d47f-94ca-a4a549589773@gmail.com> (raw)
In-Reply-To: <BN8PR21MB115693C381F65E97AB65FA18B7190@BN8PR21MB1156.namprd21.prod.outlook.com>

On 31/05/2019 16:56, Cliff Schomburg wrote:
> Wow, I did not see that in the man pages... but I see it now.  Thanks!
> 
> So I guess I would change my ask to this:
> 
> "git push -u"
> 
> Should default to "origin branch" if no parameters are provided.

I think most people will agree, considering it already works this way :)

The default behaviour of git push changed in Git 2.0, perhaps you were 
reading some old tutorial. You can configure it to match your 
preferences by changing push.default value in your git config:

https://git-scm.com/docs/git-config#Documentation/git-config.txt-pushdefault

--
Patryk Obara

  reply	other threads:[~2019-05-31 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BN8PR21MB1156ED141AE2662BC5328A22B7180@BN8PR21MB1156.namprd21.prod.outlook.com>
     [not found] ` <BN8PR21MB1156F593DAEBD7194DA7041EB7180@BN8PR21MB1156.namprd21.prod.outlook.com>
     [not found]   ` <BN8PR21MB1156DA1893F64814F1BE8709B7180@BN8PR21MB1156.namprd21.prod.outlook.com>
2019-05-31 14:45     ` Cliff Schomburg
2019-05-31 14:51       ` Patryk Obara
2019-05-31 14:56         ` Cliff Schomburg
2019-05-31 15:05           ` Patryk Obara [this message]
2019-05-31 15:13             ` Cliff Schomburg
2019-06-03 21:34               ` Cliff Schomburg
2019-05-31 15:11           ` Denton Liu

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=ebc03b4e-daf8-d47f-94ca-a4a549589773@gmail.com \
    --to=dreamer.tan@gmail.com \
    --cc=clisc@microsoft.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 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).