Re: Update local tracking refs when pushing- no way to disable

["Shawn O. Pearce" <spearce@spearce.org>]

Marco Costalba <mcostalba@gmail.com> wrote:
> On 7/6/07, Daniel Barkalow <barkalow@iabervon.org> wrote:
> >
> >(AFAICT, the only additional stuff that -a shows with git branch is the
> >stuff that you're deleting; perhaps qgit should have an option to not show
> >remotes, or not show them by default or only show them if what they point
> >to isn't otherwise marked? Anyway, it shouldn't be necessary to avoid
> >having this information just so that it isn't shown in interfaces you
> >use.)
> >
> 
> Probably an option "show remote branches" from a popup context menu
> (right click) is the more natural and predictable solution.

Recently I was faced with handling a repository that has over
200 local refs/heads and 200+ refs/remotes that the user might
be interested in working on.  Yea, its fun to look at in gitk.
It is not fun to run `git fetch` when on Cygwin.

Anyway, the git-gui `pu` branch now has new UI to handle these
sorts of cases rather nicely.  The revision selection mega-widget
that I recently wrote lets the user select which "class" of ref
(head, tracking branch, tag) they want and then filter them using
a substring glob filter.  The trick works very well to let the user
weed the list of 400+ possible refs down to just a couple that they
can pick from with the keyboard, or the mouse.

The UI will be in 0.8.0.  Which I'm hoping to go into an rc status
later this week.


Minor warning: currently the `pu` branch of git-gui probably
requires git 1.5.3-rc0 or later.  It doesn't test for it and just
assumes your git is new enough.  I do plan on fixing the couple of
spots that might matter to be conditional and fallback gracefully
if 1.5.3 isn't available.  Just haven't done it yet.  Those will
be fixed before they merge to `master`.

-- 
Shawn.