Re: [SCRIPT] git-upstream: prints the tracking chain starting at the named ref

[Petr Baudis <pasky@suse.cz>]

  Hi,

On Sat, Jul 26, 2008 at 10:44:29AM -0400, Scott Collins wrote:
> Here's a script I've sort of `grown' over the past few weeks.
>
> I use it to quickly see where a tracking branch stands with respect to 
> upstream refs _without_ actually fetching or even switching to the tracking 
> branch.  This may not be useful for everyones' work-flows; but I find it 
> handy. I'm posting because it may be of use to others (and feedback, if 
> any, can only improve it).

  I wonder why is it a problem to fetch first in your workflow? If there
is nothing for a fetch, git-upstream is going to be as fast as git fetch
&& git branch, if there is something for a fetch, you probably want to
fetch anyway if you're running this script.

  Note that in very recent Git trees, git branch -v will show some
tracking information, however it could use quite some improvement (print
something even if the branch equals the remote branch, print the
ahead/behind combination in case the branch does not fast-forward) -
maybe it might be more effective to enhance that instead?

-- 
				Petr "Pasky" Baudis
As in certain cults it is possible to kill a process if you know
its true name.  -- Ken Thompson and Dennis M. Ritchie