git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Denton Liu <liu.denton@gmail.com>
To: Cliff Schomburg <clisc@microsoft.com>
Cc: Patryk Obara <dreamer.tan@gmail.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 11:11:26 -0400	[thread overview]
Message-ID: <20190531151126.GA3465@archbookpro.localdomain> (raw)
In-Reply-To: <BN8PR21MB115693C381F65E97AB65FA18B7190@BN8PR21MB1156.namprd21.prod.outlook.com>

On Fri, May 31, 2019 at 02:56:12PM +0000, 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.  Thoughts?

I'll do you one better. You can run

	$ git push -u origin HEAD

and HEAD will mean the current branch, so you'll only need to specify
the remote (in our case, origin).

Perhaps you could alias that to something like `git push-up`.

> 
> Thanks,
> Cliff
> 
> -----Original Message-----
> From: Patryk Obara <dreamer.tan@gmail.com> 
> Sent: Friday, May 31, 2019 10:51 AM
> To: Cliff Schomburg <clisc@microsoft.com>; git@vger.kernel.org
> Subject: Re: Simple shortcut for "git push --set-upstream origin newBranchName"
> 
> On 31/05/2019 16:45, Cliff Schomburg wrote:
> > I'm proposing a shortcut for this command.
> 
> What's wrong with "$ git push -u origin branch"?
> 
> --
> Patryk Obara

      parent reply	other threads:[~2019-05-31 15:11 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     ` Simple shortcut for "git push --set-upstream origin newBranchName" Cliff Schomburg
2019-05-31 14:51       ` Patryk Obara
2019-05-31 14:56         ` Cliff Schomburg
2019-05-31 15:05           ` Patryk Obara
2019-05-31 15:13             ` Cliff Schomburg
2019-06-03 21:34               ` Cliff Schomburg
2019-05-31 15:11           ` Denton Liu [this message]

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=20190531151126.GA3465@archbookpro.localdomain \
    --to=liu.denton@gmail.com \
    --cc=clisc@microsoft.com \
    --cc=dreamer.tan@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).