git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: creating tracking branches with git gui
Date: Thu, 8 May 2008 19:41:14 -0400	[thread overview]
Message-ID: <20080508234114.GZ29038@spearce.org> (raw)
In-Reply-To: <2e24e5b90805072006j311b276cpe0a0d0eea9fa13a0@mail.gmail.com>

Sitaram Chamarty <sitaramc@gmail.com> wrote:
> 
> Over on another thread I found a config variable called
> gui.matchtrackingbranch, but setting that to true only saved me a
> mouse click -- it didn't really create the tracking, as seen by "git
> remote show origin".

Yea, I think that option actually predates the --track thing that
git-branch does these days.  Its designed to save a mouse click if
you are working in a corporate centralized repository model and
need to switch branches multiple times per day, always grabbing
the latest from the centralized repository when possible.

> On Wed, May 7, 2008 at 1:34 PM, Sitaram Chamarty <sitaramc@gmail.com> wrote:
> >
> >  Using git gui to create tracking branches only creates the local
> >  branch, but does not establish tracking.  Using the command "git
> >  branch newbr origin/newbr" works as expected of course.
> >
> >  I clicked on "Branch", then "Create", chose the "Match Tracking Branch
> >  Name" radio button, chose the appropriate branch (origin/newbr) in the
> >  list below, then finally hit Create at the bottom right.

Right.

I don't use the --track feature (branch.$name.remote, branch.$name.merge)
in my own work, so I have never had the desire or need to make sure that
git-gui sets this up for you.

I'll try to work up a patch this evening.

-- 
Shawn.

  reply	other threads:[~2008-05-08 23:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07  8:04 creating tracking branches with git gui Sitaram Chamarty
2008-05-08  3:06 ` Sitaram Chamarty
2008-05-08 23:41   ` Shawn O. Pearce [this message]
2008-05-09 18:20     ` Sitaram Chamarty

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=20080508234114.GZ29038@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=sitaramc@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).