<p dir="ltr">Right. I think the commits will show up with multiple (two, I think) projects, which should be fine.</p>
<br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 23, 2017, 02:43 Manuel Klimek <<a href="mailto:klimek@google.com">klimek@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Thu, Nov 23, 2017 at 12:58 AM Ben Hamilton <<a href="mailto:benhamilton@google.com" target="_blank">benhamilton@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Absolutely — I should have mentioned that we would keep the main rL project and continue to use it.</p></blockquote><div><br></div></div></div><div dir="ltr"><div class="gmail_quote"><div>Your original email said "Moving forward, only LLVM commits will be identified with the prefix rL (as in <a href="https://reviews.llvm.org/rL12345" target="_blank">https://reviews.llvm.org/rL12345</a>) — each project will get its own unique prefix, which might surprise some users or require changes to tools which bake in the rL prefix".</div><div><br></div><div>That seems to not be an issue, as long as all commits for all projects are still reachable under the rL tag, right?</div></div></div><div dir="ltr"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><div class="gmail_quote"><div dir="ltr">On Wed, Nov 22, 2017, 09:23 Manuel Klimek <<a href="mailto:klimek@google.com" target="_blank">klimek@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>+llvm-dev, so we get wider input :)<br></div><div><br></div>Given how unfortunate reviews that are started without cc'ing the right list are (basically folks need to re-send the review from scratch), I support this idea.<div><br></div><div>Ben, couldn't rL still be available for all projects? (and be the main project for LLVM).<br><div><br></div></div><br><div class="gmail_quote"></div></div><div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Tue, Nov 21, 2017 at 5:18 PM Ben Hamilton via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>> wrote:<br></div></div></div><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">OK. I confirmed that Stephan's process to send out cross-repo diffs from the monorepo is not affected by my proposal.<div><br></div><div>tl;dr: <a href="https://reviews.llvm.org/D40312" target="_blank">https://reviews.llvm.org/D40312</a> (which was sent out on top of D40179 to emulate what happens with a monorepo after my proposal lands).</div><div><br></div><div>Steps I took (starting with <a href="https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo" style="outline:transparent solid 1px" target="_blank">https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo</a>):<div><br></div><div>===</div>% git clone <a href="https://github.com/llvm-project/llvm-project-20170507/" target="_blank">https://github.com/llvm-project/llvm-project-20170507/</a> llvm-project<div>% cd llvm-project</div><div>% cp llvm/.arcconfig .</div><div>% mkdir -p .git/info</div><div>% echo .arcconfig >> .git/info/exclude</div><div># Manually apply D40179 into the clang-tools-extra directory</div><div><div>% arc export --revision D40179 --git | patch -d clang-tools-extra -p1</div><div>patching file .arcconfig</div></div><div><div>% git diff</div><div>diff --git a/clang-tools-extra/.arcconfig b/clang-tools-extra/.arcconfig</div><div>index f846581763e..d4a00161bce 100644</div><div>--- a/clang-tools-extra/.arcconfig</div><div>+++ b/clang-tools-extra/.arcconfig</div><div>@@ -1,4 +1,4 @@</div><div> {</div><div>- "project_id" : "clang-tools-extra",</div><div>+ "repository.callsign" : "CTE",</div><div> "conduit_uri" : "<a href="https://reviews.llvm.org/" target="_blank">https://reviews.llvm.org/</a>"</div><div> }</div></div><div><div> % git commit -a -m "Differential Revision: <a href="https://reviews.llvm.org/D40179" target="_blank">https://reviews.llvm.org/D40179</a>"</div></div><div><div> % echo "Test 1" >> llvm/README.txt </div></div><div><div> % echo "Test 2" >> clang-tools-extra/README.txt </div></div><div><div> % git commit -a -m "[Test] Monorepo test diff crossing Differential repositories" </div></div><div><div> % arc diff --create --reviewers sberg HEAD^</div></div><div>===</div></div></div><div dir="ltr"><div><div><br></div><div><div>Ben</div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Nov 21, 2017 at 8:00 AM Stephan Bergmann <<a href="mailto:sbergman@redhat.com" target="_blank">sbergman@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 11/21/2017 03:41 PM, Ben Hamilton wrote:<br>
> > My understanding was that, while there currently is no official<br>
> monorepo, it is at least possible and accepted to send single,<br>
> cross-repo patches for review. That would no longer be possible, right?<br>
><br>
> I assume cross-repo patches would be constructed by hand, right? Or do<br>
> you mean using the unofficial monorepo from 2016<br>
> <<a href="https://github.com/joker-eph/llvm-project" rel="noreferrer" target="_blank">https://github.com/joker-eph/llvm-project</a>>?<br>
<br>
I'm using <<a href="https://github.com/llvm-project/llvm-project-20170507" rel="noreferrer" target="_blank">https://github.com/llvm-project/llvm-project-20170507</a>> (as<br>
advertised at<br>
<<a href="https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo" rel="noreferrer" target="_blank">https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo</a>>),<br>
where such a "cross-repo diff" is just a matter of a plain 'git diff'.<br>
<br>
> An example of an existing cross-repo review in Differential would be<br>
> nice—do you happen to have one handy?<br>
<br>
I just happened to file <<a href="https://reviews.llvm.org/D40295" rel="noreferrer" target="_blank">https://reviews.llvm.org/D40295</a>> a moment ago,<br>
spanning clang and compiler-rt.<br>
<br>
> I think either way, we'd keep the ability to send cross-repo patches to<br>
> the top-level LLVM repo just the same way you could today.<br>
><br>
> I'll confirm that if you can help me construct an example cross-repo<br>
> patch for review.<br>
<br>
Thanks,<br>
Stephan<br>
</blockquote></div></blockquote></div></div><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
</blockquote></div></div>
</blockquote></div>
</blockquote></div></div></blockquote></div>