search for: r56789

...gt;> with scripting and such that would extend this mechanism. >> > > This seems like a great idea to me. > >> * Proposal * >> >> 1. Use [Fix] for commit related to bug fixes. > > a specific form would be best: [Fix] PR12345, or [FIX] Bug introduced in r56789. The first line of the commit is interpreted as a "title" by "git based" tools. I rather have a self-contained first line and avoid *any* external reference there. (The commit message can be as long as you want). -- Mehdi > >> 2. Add a description of the proble...

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