mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Patryk Obara <>
To: Cliff Schomburg <>,
	"" <>
Subject: Re: Simple shortcut for "git push --set-upstream origin newBranchName"
Date: Fri, 31 May 2019 16:51:06 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
2019-05-31 14:45     ` Simple shortcut for "git push --set-upstream origin newBranchName" Cliff Schomburg
2019-05-31 14:51       ` Patryk Obara [this message]
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

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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

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).