Re: [PATCH] Add --remotes option to show-branch

From: Brian Gernhardt <benji@silverinsanity.com>
Date: Dec 19, 2006, 05:17 UTC
Message-ID: <5D50A3C0-4521-402B-ABD4-5698870A3BD2@silverinsanity.com>
In-Reply-To: <7vfybdvsq7.fsf@assigned-by-dhcp.cox.net>

On Dec 18, 2006, at 3:45 PM, Junio C Hamano wrote:

Show 18 quoted lines

> I've never used --heads and --tags myself because
>
> 	git show-branch heads/*
>         git show-branch tags/*
>
> works perfectly well for me, and it often is not very useful to
> look at _all_ the heads (tags are even much less interesting) in
> a topic heavy repository anyway.  IOW, I more often do something
> like:
>
> 	git show-branch --topics master heads/js/*
>
> to see what Johannes has relative to "master".
>
> I actually was thinking about removing these flags, not adding
> --remotes, because
>
> 	git show-branch remotes/origin/*

I agree that tags/* is fairly useless. Way too much data. And if you want to remote --heads and --tags, then --remotes doesn't have much place. I was simply poking around and thought that if we have those two, then the third seemed natural and odd to miss.

However if --all meant all heads, local or remote, I'd be fairly pleased. heads/* is just as easy as --heads (and leaving it blank is even easier), but --remotes is significantly easier than "remotes/ origin/* remotes/partner/*". And sometimes I'd really like to know where all the branches are in relation to each other.

Pardon if this doesn't make much sense.  It's been a looooong day...