git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tay Ray Chuan <rctay89@gmail.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: branch --set-upstream considered harmful
Date: Mon, 7 Jun 2010 13:10:07 +0800	[thread overview]
Message-ID: <AANLkTikUkkWQl7cYuPiKGaJFYL_JlIGFCXXf7En8t0FN@mail.gmail.com> (raw)
In-Reply-To: <AANLkTiln_xxnF-e33YA7kkfbBBcBMd40xag8JTW0eqws@mail.gmail.com>

Hi,

On Mon, Jun 7, 2010 at 3:21 AM, Jay Soffian <jaysoffian@gmail.com> wrote:
> Say I have an existing branch and it doesn't have a tracking config.
> (My local users often just do "checkout -b topic" instead of "checkout
> -b topic origin/master".)
>
> I would naively expect this to work, while on that branch:
>
>  (topic)$ git branch --set-upstream origin/master

Hmm, I can see where the confusion is coming from - you're treating
git-branch as a "branch modifier", when it really is a "branch
creator" - unless you use -f, of course.

> [snip]
> So here's how I'm thinking about fixing it, but maybe I'm just making
> it even more confusing. What say you:
>
>  (topic)$ git branch --set-upstream=origin/master
>  Branch topic set up to track remote branch master from origin.

I was under the impression that long-style options took "=".

-- 
Cheers,
Ray Chuan

  reply	other threads:[~2010-06-07  5:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-06 19:21 branch --set-upstream considered harmful Jay Soffian
2010-06-07  5:10 ` Tay Ray Chuan [this message]
2010-06-07  5:19   ` Jay Soffian
2010-06-07  6:37     ` Thomas Rast
2010-06-07  7:37       ` Jay Soffian
2010-06-07  8:44 ` Michael J Gruber

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=AANLkTikUkkWQl7cYuPiKGaJFYL_JlIGFCXXf7En8t0FN@mail.gmail.com \
    --to=rctay89@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jaysoffian@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;
as well as URLs for NNTP newsgroup(s).