{"thread":{"id":"31075","subject":"Enhanced git branch list (proposal)","startedAt":"2012-07-23T18:17:47Z","lastAt":"2012-07-24T16:40:26Z","messageCount":3,"participants":["John Bartholomew","Thomas Rast","Phil Hord"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"195537","messageId":"500D954B.4090007@gmail.com","threadId":"31075","inReplyTo":null,"subject":"Enhanced git branch list (proposal)","fromName":"John Bartholomew","fromEmail":"jpa.bartholomew@gmail.com","sentAt":"2012-07-23T18:17:47Z","receivedAt":"2012-07-23T18:17:47Z","isPatch":false,"sender":{"key":"jpa.bartholomew@gmail.com","avatar":null},"body":"I find the output of `git branch' to be quite bare, and would like to\nsee more information; most importantly, what the state of the branch\nis in relation to its upstream. For some time I have been using my\nown script to do this. It produces output like this:\n\n$ git lsb\n commodity-market-lua [behind 'brianetta/commodity-market-lua' by 2\ncommits]\n filesystem [up-to-date with 'jpab/filesystem']\n fix-ring-blending [ahead of 'jpab/fix-ring-blending' by 1 commit]\n galaxy-refactor\n galaxy-refactor-2 [diverged from 'jpab/galaxy-refactor', by 6\ncommits/626 commits (us/them)]\n hud-pitch-ladder [up-to-date with 'jpab/hud-pitch-ladder']\n= issue-1388\n issue-695\n lmr-mtllib-improvements\n marcel-stations\n* master [up-to-date with 'jpab/master']\n refcounted-body [up-to-date with 'jpab/refcounted-body']\n string-formatter [up-to-date with 'jpab/string-formatter']\n\nThe first column indicates the relation to HEAD: '*' marks the current\nhead, '=' marks a branch which is identical with the current HEAD.\n\nBranches which have a configured upstream (branch.remote and\nbranch.merge are set) show the relation to the corresponding remote\nbranch.\n\nSome key text ('up-to-date', 'ahead', 'behind' or 'diverged', and the\nname of the current HEAD) is displayed with colour if colour is\nenabled.\n\nArguments can be passed to show remote branches (for all remotes, or\nfor a specified remote), or all branches, and to show each branch\nin relation to a specified target branch instead of the configured\nremote tracking branch.\n\nI would like to know whether there is any interest in incorporating\nthis functionality into the main git distribution, either as a\nseparate command, or within `git branch'. For my purposes I have it\naliased under the name `git lsb' for `list branches'.\n\nYou can examine the script I'm using for this at:\n\nhttps://github.com/johnbartholomew/gitvoodoo/blob/master/bin/git-xbranch\n\nRegards,\n\nJohn B\n"},{"id":"195545","messageId":"87eho2tjji.fsf@thomas.inf.ethz.ch","threadId":"31075","inReplyTo":"500D954B.4090007@gmail.com","subject":"Re: Enhanced git branch list (proposal)","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2012-07-23T18:32:49Z","receivedAt":"2012-07-23T18:32:49Z","isPatch":false,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"John Bartholomew writes:\n\n> I find the output of `git branch' to be quite bare, and would like to\n> see more information; most importantly, what the state of the branch\n> is in relation to its upstream.\n\nThat is already present: just run git branch -vv.\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"},{"id":"195635","messageId":"CABURp0qcisya1MEL=2CMpuERjmpRm=PZ_doUurcwa1MQERTATw@mail.gmail.com","threadId":"31075","inReplyTo":"500D954B.4090007@gmail.com","subject":"Re: Enhanced git branch list (proposal)","fromName":"Phil Hord","fromEmail":"phil.hord@gmail.com","sentAt":"2012-07-24T16:40:26Z","receivedAt":"2012-07-24T16:40:26Z","isPatch":false,"sender":{"key":"phil.hord@gmail.com","avatar":"https://avatars.githubusercontent.com/u/123908?v=4"},"body":"On Mon, Jul 23, 2012 at 2:17 PM, John Bartholomew\n wrote:\n>\n> I find the output of `git branch' to be quite bare, and would like to\n> see more information; most importantly, what the state of the branch\n> is in relation to its upstream. For some time I have been using my\n> own script to do this. It produces output like this:\n>\n> $ git lsb\n> commodity-market-lua [behind 'brianetta/commodity-market-lua' by 2\n> commits]\n> filesystem [up-to-date with 'jpab/filesystem']\n> fix-ring-blending [ahead of 'jpab/fix-ring-blending' by 1 commit]\n> galaxy-refactor\n> galaxy-refactor-2 [diverged from 'jpab/galaxy-refactor', by 6\n> commits/626 commits (us/them)]\n> hud-pitch-ladder [up-to-date with 'jpab/hud-pitch-ladder']\n> = issue-1388\n> issue-695\n> lmr-mtllib-improvements\n> marcel-stations\n> * master [up-to-date with 'jpab/master']\n> refcounted-body [up-to-date with 'jpab/refcounted-body']\n> string-formatter [up-to-date with 'jpab/string-formatter']\n>\n> The first column indicates the relation to HEAD: '*' marks the current\n> head, '=' marks a branch which is identical with the current HEAD.\n>\n> Branches which have a configured upstream (branch.remote and\n> branch.merge are set) show the relation to the corresponding remote\n> branch.\n>\n> Some key text ('up-to-date', 'ahead', 'behind' or 'diverged', and the\n> name of the current HEAD) is displayed with colour if colour is\n> enabled.\n>\n> Arguments can be passed to show remote branches (for all remotes, or\n> for a specified remote), or all branches, and to show each branch\n> in relation to a specified target branch instead of the configured\n> remote tracking branch.\n>\n> I would like to know whether there is any interest in incorporating\n> this functionality into the main git distribution, either as a\n> separate command, or within `git branch'. For my purposes I have it\n> aliased under the name `git lsb' for `list branches'.\n>\n> You can examine the script I'm using for this at:\n> https://github.com/johnbartholomew/gitvoodoo/blob/master/bin/git-xbranch\n\nThanks. You might also find this one interesting:\n\nhttp://masanjin.net/blog/label/git-wtf/\n\nPhil\n"}]}