search for: prnnn

...like [Fix] would do. >> Thanks to that tag, it would be possible to easily filter bug fixes in email and other cherry-picking helper tools, I believe. > > If we really do want to make a guideline about this, I propose we > standardize on suffixing the first line of the commit with (PRnnn). That would work for me. Anywhere in the commit message would work as well (like Mehdi and Hal said), though I tend to prefer the first line (but Mehdi does not like it :)). Cheers, -Quentin > > Cheers, > Hans

Hi, I am sending this proposal to get feedbacks on how we could make the tagging of bug fixes and regressions more obvious. The idea is to provide easily accessible information to help deciding what to cherry-pick in a release branch. * Context * People shipping compilers based on LLVM may not completely align with the official releases of LLVM. Thus, the stabilization of each custom release

...t;> Thanks to that tag, it would be possible to easily filter bug fixes in email and other cherry-picking helper tools, I believe. >>> >>> If we really do want to make a guideline about this, I propose we >>> standardize on suffixing the first line of the commit with (PRnnn). >> >> That would work for me. >> >> Anywhere in the commit message would work as well (like Mehdi and Hal said), though I tend to prefer the first line (but Mehdi does not like it :)). >> >> Cheers, >> -Quentin >> >>> >>> Chee...