On Wed, Aug 5, 2015 at 7:47 PM, Ivan Chernyavsky <campo...@yandex.ru> wrote: > Dear community, > > For some time I'm wondering why there's no "--grep" option to the "git > branch" command, which would request to print only branches having specified > string/regexp in their history.
Probably because nobody is interested and steps up to do it. The lack of response to you mail is a sign. Maybe you can try make a patch? I imagine it would not be so different from current --contains code, but this time we need to look into commits, not just commit id. > So for example: > > $ git branch -r --grep=BUG12345 > > should be roughly equivalent to following expression I'm using now for the > same task: > > $ for r in `git rev-list --grep=BUG12345 --remotes=origin`; do git branch > -r --list --contains=$r 'origin/*'; done | sort -u > > Am I missing something, is there some smarter/simpler way to do this? > > Thanks a lot in advance! > > -- > Ivan > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
