{"thread":{"id":"35436","subject":"feature request: consider picked commits in \"branch --contains\"","startedAt":"2013-11-29T17:45:35Z","lastAt":"2013-11-29T17:45:35Z","messageCount":1,"participants":["Ralf Thielow"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"231272","messageId":"CAN0XMOL60kX4TkPkop3wA1p5dgLMh0i7_=5mB1Gwwg620QRedA@mail.gmail.com","threadId":"35436","inReplyTo":null,"subject":"feature request: consider picked commits in \"branch --contains\"","fromName":"Ralf Thielow","fromEmail":"ralf.thielow@gmail.com","sentAt":"2013-11-29T17:45:35Z","receivedAt":"2013-11-29T17:45:35Z","isPatch":false,"sender":{"key":"ralf.thielow@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1275832?v=4"},"body":"Hi,\n\nthere are development workflows where a feature or fix is\nby definition implemented in the dev branch and perhaps picked\ninto a stable/rc branch.\nA question often being asked in such a workflow is \"Is this fix in this\nstable branch?\". Usually I would call \"git branch -r --contains $commit\"\nto figure this out, but this command does not work in such workflows\nbecause it's a different commit since it was picked.\ngit-log knows the --cherry-pick option to identify commits with identical\nchanges.\nWouldn't it be nice to say \"git branch --cherry-pick --contains $commit\"\nto see branches containing a commit even if the commit was picked?!\n\nRalf\n"}]}