search for: d40312

...> OK. I confirmed that Stephan's process to send out cross-repo diffs from > the monorepo is not affected by my proposal. > > I'm a bit late to the party, and I might just not have comprehended this correctly. But does your example actually work? I didn't see any email about D40312 on llvm-commits, shouldn't there have been one? Also, how would arcanist pick up two callsigns here? Wouldn't it just pick the from the closest surrounding .arcconfig? tl;dr: https://reviews.llvm.org/D40312 (which was sent out on top of D40179 > to emulate what happens with a monorepo...

.../llvm/trunk/.arcconfig>. > > I haven't committed any changes to that .arcconfig yet, and in addition > there aren't yet any Herald rules which copy llvm-commits@ on review > requests sent out to the LLVM project. > > So, that explains why llvm-commits@ was not copied on D40312. > > The previous setup made sense, since review requests for clang et al were > also lumped together in the rL LLVM Diffusion repository > <https://reviews.llvm.org/diffusion/L/>, and we didn't want to subscribe > llvm-commits@ on those. > > Once I land the set of co...

...t;. >> >> I haven't committed any changes to that .arcconfig yet, and in addition >> there aren't yet any Herald rules which copy llvm-commits@ on review >> requests sent out to the LLVM project. >> >> So, that explains why llvm-commits@ was not copied on D40312. >> >> The previous setup made sense, since review requests for clang et al were >> also lumped together in the rL LLVM Diffusion repository >> <https://reviews.llvm.org/diffusion/L/>, and we didn't want to subscribe >> llvm-commits@ on those. >> >&g...

...main project for LLVM). On Tue, Nov 21, 2017 at 5:18 PM Ben Hamilton via cfe-dev < cfe-dev at lists.llvm.org> wrote: > OK. I confirmed that Stephan's process to send out cross-repo diffs from > the monorepo is not affected by my proposal. > > tl;dr: https://reviews.llvm.org/D40312 (which was sent out on top of > D40179 to emulate what happens with a monorepo after my proposal lands). > > Steps I took (starting with > https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo > ): > > === > % git clone https://github.com/llvm-...

...5:18 PM Ben Hamilton via cfe-dev < >> cfe-dev at lists.llvm.org> wrote: >> >>> OK. I confirmed that Stephan's process to send out cross-repo diffs from >>> the monorepo is not affected by my proposal. >>> >>> tl;dr: https://reviews.llvm.org/D40312 (which was sent out on top of >>> D40179 to emulate what happens with a monorepo after my proposal lands). >>> >>> Steps I took (starting with >>> https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo >>> ): >>> &g...