Sorry for empty subject in the original mail, somehow I've deleted it and didn't even notice.
05.08.2015, 20:05, "Junio C Hamano" <[email protected]>: > Junio C Hamano <[email protected]> writes: > >> I think people do things like: >> >> git log --all --decorate --grep=... > > s/decorate/source/; sorry for the noise. Thanks Junio! I was actually considering using --source, but for me the problem is it always returns *just one* branch for every matching commit. So the caller must then use his own knowledge to deduce all branches where this branch merged. Considering following history: * b46f30e refs/heads/zzz eee | * dc0280f refs/heads/yyy ddd |/ | * 31739da refs/heads/xxx ccc |/ * a42bd23 refs/heads/master bbb * 01a8291 refs/heads/master aaa Command "git log --all --source --grep=bbb --oneline" will return: a42bd23 refs/heads/master bbb While I'm expecting something like "git branch --contains=a42bd23" output in terms of *all* topics being listed: master xxx yyy * zzz The most common use case is when support people need to quickly get at least rough idea which branches have specific ticket/CR mentioned. -- Ivan -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
