Re: best way to fastforward all tracking branches after a fetch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



(sorry about that previous email; hit send in error.  Here's the complete one)

On Mon, Dec 19, 2011 at 12:01 PM, Nazri Ramliy <ayiehere@xxxxxxxxx> wrote:
> On Sat, Dec 17, 2011 at 6:11 PM, Sitaram Chamarty <sitaramc@xxxxxxxxx> wrote:
>> oops; forgot the program...
>
> This is nice!
>
> Stick it on github, or somewhere, please, so that I can always get the
> latest and greatest?
>
> Thanks.
>
> nazri

ok; it's on github: http://github.com/sitaramc/git-tools (they're all
standalone tools; you don't have to use the others)

The output is now colorised, and it will now also tell you, for each
remote you have, what branches you are hiding from them and what they
have which you have not started tracking locally.

a "screenshot" is at
http://sitaramc.github.com/git-tools/index.html#index_git_branch_check_

I notice I'm using it more and more, often even as a replacement for
'git status'... at least for repos where I'm juggling multiple
remotes.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]