From: Andreas Schwab <schwab@linux-m68k.org>
To: Bradley Wagner <bradley.wagner@hannonhill.com>
Cc: git@vger.kernel.org
Subject: Re: Pushing a new branch to a remote and tracking it
Date: Wed, 28 Jul 2010 00:35:25 +0200 [thread overview]
Message-ID: <m26300o8nm.fsf@igel.home> (raw)
In-Reply-To: <AANLkTikxmhndNqGDpwfBm41OuaPvnB=2xqp6gkYOTQiF@mail.gmail.com> (Bradley Wagner's message of "Tue, 27 Jul 2010 18:12:09 -0400")
Bradley Wagner <bradley.wagner@hannonhill.com> writes:
> Is there a more elegant way to: 1) create a branch, 2) push it to a
> remote and 3) continue to track it.
git push --set-upstream (since v1.7.0)
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-07-27 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 22:12 Pushing a new branch to a remote and tracking it Bradley Wagner
2010-07-27 22:35 ` Andreas Schwab [this message]
2010-07-28 1:20 ` Bradley Wagner
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=m26300o8nm.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=bradley.wagner@hannonhill.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.
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 NNTP newsgroup(s).