Dnia środa, 23 stycznia 2019 18:49:46 CET Thiago Macieira pisze: > On Wednesday, 23 January 2019 08:37:57 PST Konstantin Tokarev wrote: > > > Disadvantages: > > > - git history would be a bit wilder, "git branch --contains" would not > > > work > > > - commit messages in some branches would have kind of ugly footer as > > > an > > > > > > effect of "cherry-pick -x" > > > > Gerrit's Change-Id can be used to track presence of patch in branches of > > interest > > Yes, but not as easily, since the git branch --contains and git tag > --contains are pure DAG operations. The search you're talking about is a > text search (usually implemented by a regexp search) on the commit message, > with no DAG boundaries. You have to scan all valid branches for a given > string. > > And then you still have to run git branch --contains on each entry you found > to figure out which branches contain those commits. > > So this is scriptable. It's going to be something like 100x slower than > today, but it should still finish within 10 seconds, even on slow machines.
As we would not be the only one using it, I bet the script could be upstream'ed to git. Cheers, Jędrek _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development