Re: best way to fastforward all tracking branches after a fetch
- From
Sitaram Chamarty <sitaramc@gmail.com>
- Date
- Jan 18, 2012, 01:50 UTC
- Message-ID
- <CAMK1S_hK_shh5g8BOxhKz3tw2m=kp6qZM1ZTQOOnY2eMNzL3hA@mail.gmail.com>
- In-Reply-To
- <CAEY4ZpPKLrWQpEUYkwST8Fh40JwrjxvD+6yML6A+=XpsYmPevg@mail.gmail.com>
(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@gmail.com> wrote:
Show 11 quoted lines
> On Sat, Dec 17, 2011 at 6:11 PM, Sitaram Chamarty <sitaramc@gmail.com> 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.