{"thread":{"id":"32155","subject":"[wishlist] support git flow-like view","startedAt":"2012-11-20T23:42:52Z","lastAt":"2012-11-21T16:43:41Z","messageCount":7,"participants":["Lisandro Damián Nicanor Pérez Meyer","Andrew Ardill","Johannes Sixt","Holger Hellmuth (IKS)"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"203582","messageId":"201211202043.00293.perezmeyer@gmail.com","threadId":"32155","inReplyTo":null,"subject":"[wishlist] support git flow-like view","fromName":"Lisandro Damián Nicanor Pérez Meyer","fromEmail":"perezmeyer@gmail.com","sentAt":"2012-11-20T23:42:52Z","receivedAt":"2012-11-20T23:42:52Z","isPatch":false,"sender":{"key":"perezmeyer@gmail.com","avatar":"https://gravatar.com/avatar/27830ece3a4fbece57177e521e65696225408a930e3e11b94a172425e336235e?d=mp&s=160"},"body":"Hi! I am not suscribed to the list, so please CC-me.\n\nI think this may have been proposed before, but I could not find anything in \nthe web, so I better try myself :)\n\nThe idea would be to gitk to show a \"git flow-like\"[0] view when it detects \ngit flow (or the user ask for it or...)\n\nBasiccaly, you can show the main two branches: master and develop. Of course, \nhaving the possibility to show feature/release/hotfixes branches would be \nideal.\n\nKinds regards, Lisandro.\n\n[0] \n\n\n-- \nEsperando confirmación de ingredientes necesarios\nque serán expuestos a la radiación...\n Manera geek de expresar que se espera la compra\n de carne para un típico asado argentino.\n Silvio Rikemberg.\n\nLisandro Damián Nicanor Pérez Meyer\nhttp://perezmeyer.com.ar/\nhttp://perezmeyer.blogspot.com/\n"},{"id":"203584","messageId":"CAH5451nrcEo3Uxm0x6b39Hq1k-J4=OZPi-Cao7osaiS-w_Z1+Q@mail.gmail.com","threadId":"32155","inReplyTo":"201211202043.00293.perezmeyer@gmail.com","subject":"Re: [wishlist] support git flow-like view","fromName":"Andrew Ardill","fromEmail":"andrew.ardill@gmail.com","sentAt":"2012-11-20T23:56:26Z","receivedAt":"2012-11-20T23:56:26Z","isPatch":false,"sender":{"key":"andrew.ardill@gmail.com","avatar":"https://gravatar.com/avatar/da14cb7c091dd44dc6c63a4d3361b149acaf25226dc78eb4131a17b93d9b0993?d=mp&s=160"},"body":"On 21 November 2012 10:42, Lisandro Damián Nicanor Pérez Meyer\n wrote:\n>\n> Hi! I am not suscribed to the list, so please CC-me.\n\nThat is the default etiquette on this list :)\n\n> I think this may have been proposed before, but I could not find anything in\n> the web, so I better try myself :)\n>\n> The idea would be to gitk to show a \"git flow-like\"[0] view when it detects\n> git flow (or the user ask for it or...)\n\nWhat does it mean to 'show a \"git flow-like\" view'? Show multiple\nbranches? Place commits on each branch in 'swim-lanes', rather than\nmoving them around on the horizontal to fit the space available? Some\nmore detail, or even a mock-up would help a lot here.\n\n> Basiccaly, you can show the main two branches: master and develop. Of course,\n> having the possibility to show feature/release/hotfixes branches would be\n> ideal.\n\nIt is already possible to show multiple branches in gitk at the same\ntime. You probably have some more specific needs beyond simply showing\nthe different branches. Maybe you can be more specific?\n\nRegards,\n\nAndrew Ardill\n"},{"id":"203587","messageId":"201211202113.44459.perezmeyer@gmail.com","threadId":"32155","inReplyTo":"CAH5451nrcEo3Uxm0x6b39Hq1k-J4=OZPi-Cao7osaiS-w_Z1+Q@mail.gmail.com","subject":"Re: [wishlist] support git flow-like view","fromName":"Lisandro Damián Nicanor Pérez Meyer","fromEmail":"perezmeyer@gmail.com","sentAt":"2012-11-21T00:13:36Z","receivedAt":"2012-11-21T00:13:36Z","isPatch":false,"sender":{"key":"perezmeyer@gmail.com","avatar":"https://gravatar.com/avatar/27830ece3a4fbece57177e521e65696225408a930e3e11b94a172425e336235e?d=mp&s=160"},"body":"On Tue 20 Nov 2012 20:56:26 Andrew Ardill escribió:\n> On 21 November 2012 10:42, Lisandro Damián Nicanor Pérez Meyer\n> \n> wrote:\n> > Hi! I am not suscribed to the list, so please CC-me.\n> \n> That is the default etiquette on this list :)\n\nGreat :-)\n \n> > I think this may have been proposed before, but I could not find anything\n> > in the web, so I better try myself :)\n> > \n> > The idea would be to gitk to show a \"git flow-like\"[0] view when it\n> > detects git flow (or the user ask for it or...)\n> \n> What does it mean to 'show a \"git flow-like\" view'? Show multiple\n> branches? Place commits on each branch in 'swim-lanes', rather than\n> moving them around on the horizontal to fit the space available? Some\n> more detail, or even a mock-up would help a lot here.\n\nI think the best mock-up would be:\n\n\n\nYes, I'm referring to \"swim-lanes\" like view. Which may be already there and \nI'm miserably failing to see :-/\n\n> > Basiccaly, you can show the main two branches: master and develop. Of\n> > course, having the possibility to show feature/release/hotfixes branches\n> > would be ideal.\n> \n> It is already possible to show multiple branches in gitk at the same\n> time. You probably have some more specific needs beyond simply showing\n> the different branches. Maybe you can be more specific?\n\nWell, two ideas come to my mind:\n\n- detect when using git flow (.git/config contains [gitflow \"some_branch\"] \nentries).\n- Show \"swim-lane\"-like graphs, including branches that may not be present, \nbut where there (release branches often are created and merged back, for \nexample)\n\nMaybe some of this is already there and/or it's too much trouble to do so, in \nthose cases, please accept my apologies :-)\n\nKinds regards, Lisandro.\n\n-- \nLisandro Damián Nicanor Pérez Meyer\nhttp://perezmeyer.com.ar/\nhttp://perezmeyer.blogspot.com/\n"},{"id":"203588","messageId":"CAH5451nsOE+VkrC7YaSEWYcUd5q2vMze5QPoVGWY8Q+T=nSvww@mail.gmail.com","threadId":"32155","inReplyTo":"201211202113.44459.perezmeyer@gmail.com","subject":"Re: [wishlist] support git flow-like view","fromName":"Andrew Ardill","fromEmail":"andrew.ardill@gmail.com","sentAt":"2012-11-21T01:54:09Z","receivedAt":"2012-11-21T01:54:09Z","isPatch":false,"sender":{"key":"andrew.ardill@gmail.com","avatar":"https://gravatar.com/avatar/da14cb7c091dd44dc6c63a4d3361b149acaf25226dc78eb4131a17b93d9b0993?d=mp&s=160"},"body":"On 21 November 2012 11:13, Lisandro Damián Nicanor Pérez Meyer\n wrote:\n> ...\n> Well, two ideas come to my mind:\n>\n> - detect when using git flow (.git/config contains [gitflow \"some_branch\"]\n> entries).\n\nI guess this part is just so the next part can be done automatically?\n\n> - Show \"swim-lane\"-like graphs, including branches that may not be present,\n> but where there (release branches often are created and merged back, for\n> example)\n\nI think this could be useful in general, however it might struggle\nwith already merged branches. I may be mistaken here, however I think\nin general there is no way to specify which commits belonged to a\ncertain branch after they have been merged, as branch information is\nnot kept in the commit object. There may be some exceptions that make\nit feasible at times, but a general solution would be to show any\nmerged branches as part of the same swim-lane, as per current\nbehaviour, but to have separate branch heads in different swim-lanes.\nThis would be a nice feature, and is similar to the behaviour in, for\nexample, Atlassian's Fisheye repository viewer and the GitHub network\nview.\n\nRegards,\n\nAndrew Ardill\n"},{"id":"203597","messageId":"50AC7C49.6050004@viscovery.net","threadId":"32155","inReplyTo":"201211202113.44459.perezmeyer@gmail.com","subject":"Re: [wishlist] support git flow-like view","fromName":"Johannes Sixt","fromEmail":"j.sixt@viscovery.net","sentAt":"2012-11-21T07:01:29Z","receivedAt":"2012-11-21T07:01:29Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Am 11/21/2012 1:13, schrieb Lisandro Damián Nicanor Pérez Meyer:\n> I think the best mock-up would be:\n> \n> \n> \n> Yes, I'm referring to \"swim-lanes\" like view. Which may be already there and \n> I'm miserably failing to see :-/\nMaybe you are just looking for gitk --date-order --branches?\n\n-- Hannes\n"},{"id":"203602","messageId":"50ACEA95.9020909@ira.uka.de","threadId":"32155","inReplyTo":"201211202113.44459.perezmeyer@gmail.com","subject":"Re: [wishlist] support git flow-like view","fromName":"Holger Hellmuth (IKS)","fromEmail":"hellmuth@ira.uka.de","sentAt":"2012-11-21T14:52:05Z","receivedAt":"2012-11-21T14:52:05Z","isPatch":false,"sender":{"key":"hellmuth@ira.uka.de","avatar":null},"body":"Am 21.11.2012 01:13, schrieb Lisandro Damián Nicanor Pérez Meyer:\n> Well, two ideas come to my mind:\n>\n> - detect when using git flow (.git/config contains [gitflow \"some_branch\"]\n> entries).\n\nShouldn't it be part of the gitflow package then?\n\n> - Show \"swim-lane\"-like graphs, including branches that may not be present,\n> but where there (release branches often are created and merged back, for\n> example)\n\nAs a general feature there could be a config option gitk reads with an \nordered list of branch names (with wildcards). Those branches would \nalways be printed in gitk as the leftmost branches (i.e. have their own \nlane on the left side). All other branches would be shown normally.\n\nThis would give you part of what you want, a special lane at least for \nmaster and develop and for branches you can group under wildcard branch \nnames (for example if you prefix all release branches with \"rel-\").\n\nAnd it would give others the ability to make special branches in gitk \nmore visible.\n\n(Yes I know, I'm talking again of stuff I won't have time or ability to \nimplement ;-). Sigh)\n"},{"id":"203604","messageId":"201211211343.42187.perezmeyer@gmail.com","threadId":"32155","inReplyTo":"50ACEA95.9020909@ira.uka.de","subject":"Re: [wishlist] support git flow-like view","fromName":"Lisandro Damián Nicanor Pérez Meyer","fromEmail":"perezmeyer@gmail.com","sentAt":"2012-11-21T16:43:41Z","receivedAt":"2012-11-21T16:43:41Z","isPatch":false,"sender":{"key":"perezmeyer@gmail.com","avatar":"https://gravatar.com/avatar/27830ece3a4fbece57177e521e65696225408a930e3e11b94a172425e336235e?d=mp&s=160"},"body":"On Wed 21 Nov 2012 11:52:05 Holger Hellmuth (IKS) escribió:\n> Am 21.11.2012 01:13, schrieb Lisandro Damián Nicanor Pérez Meyer:\n> > Well, two ideas come to my mind:\n> > \n> > - detect when using git flow (.git/config contains [gitflow\n> > \"some_branch\"] entries).\n> \n> Shouldn't it be part of the gitflow package then?\n> \n> > - Show \"swim-lane\"-like graphs, including branches that may not be\n> > present, but where there (release branches often are created and merged\n> > back, for example)\n> \n> As a general feature there could be a config option gitk reads with an\n> ordered list of branch names (with wildcards). Those branches would\n> always be printed in gitk as the leftmost branches (i.e. have their own\n> lane on the left side). All other branches would be shown normally.\n> \n> This would give you part of what you want, a special lane at least for\n> master and develop and for branches you can group under wildcard branch\n> names (for example if you prefix all release branches with \"rel-\").\n> \n> And it would give others the ability to make special branches in gitk\n> more visible.\n> \n> (Yes I know, I'm talking again of stuff I won't have time or ability to\n> implement ;-). Sigh)\n\nThat seems an interesting idea, indeed. Thanks!\n\n-- \nEither he's dead or my watch has stopped.\n -- Groucho Marx\n\nLisandro Damián Nicanor Pérez Meyer\nhttp://perezmeyer.com.ar/\nhttp://perezmeyer.blogspot.com/\n"}]}