Re: [llvm-dev] Zorg migration to GitHub/monorepo

2019-10-29 Thread Galina Kistanova via cfe-commits
Thanks for explaining, Diana. And you are welcome. I’m glad this is not an issue with missing changes or something. Thanks Galina On Tue, Oct 29, 2019 at 1:48 AM Diana Picus wrote: > > Hi Galina, > > On Tue, 29 Oct 2019 at 04:42, Galina Kistanova wrote: > > > > Hello Nemanja, > > > > > a commi

Re: [llvm-dev] Zorg migration to GitHub/monorepo

2019-10-29 Thread Diana Picus via cfe-commits
Hi Galina, On Tue, 29 Oct 2019 at 04:42, Galina Kistanova wrote: > > Hello Nemanja, > > > a commit to a project that shouldn't trigger builds on a libcxx bot (i.e. > > the change was in llvm). > > With all due respect, this does not sound right. > I'm not sure how changes in a code a particular

Re: [llvm-dev] Zorg migration to GitHub/monorepo

2019-10-28 Thread Galina Kistanova via cfe-commits
Hello Nemanja, > a commit to a project that shouldn't trigger builds on a libcxx bot (i.e. the > change was in llvm). With all due respect, this does not sound right. I'm not sure how changes in a code a particular bot builds and tests should not trigger builds. In many cases this will lead to f

Re: [llvm-dev] Zorg migration to GitHub/monorepo

2019-10-28 Thread Nemanja Ivanovic via cfe-commits
I think what she is referring to was that the build seemed to be triggered by a commit to a project that shouldn't trigger builds on a libcxx bot (i.e. the change was in llvm). I have a somewhat orthogonal but related question. In the past, commits to compiler-rt did not trigger builds on llvm/cla