<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">Yes, I’m still trying to evaluate the migration script’s downsides as compared to the zipper approach’s downsides. Sorry that I got a little held up, but I have to balance evaluating this with getting other work done. </div><div dir="ltr"><br></div><div dir="ltr">I should have some feedback to a few of the responses on this thread next week. I really don’t think I can respond in a useful/productive way before I’ve finished these experiments.</div><div dir="ltr"><br>On Nov 15, 2018, at 16:07, Chandler Carruth via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">I think Justin was still experimenting a bit w/ the migration script. I'd like to at least let him get back to this with the results of that?</div><br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 15, 2018 at 2:55 PM James Y Knight via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</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 dir="ltr">Based on the feedback so far, I propose that we call this discussion done -- we will not go with this zippered proposal, but will proceed with <a href="https://github.com/llvm-git-prototype/llvm/" target="_blank">https://github.com/llvm-git-prototype/llvm/</a>.</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 15, 2018 at 5:06 PM David Greene via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Tom Stellard via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> writes:<br>
<br>
> What is the status with this proposal? It has been 2 weeks now since<br>
> the initial email and it seems like the discussion is slowing down. Do<br>
> we still want to consider this zippered approach as a possibility for the<br>
> official repo? <br>
<br>
I have very strong feedback from the engineer who does our upstream<br>
merges that he does NOT want to see this zippered repository. A clean<br>
linear history makes understanding merges much easier.<br>
<br>
James made a number of other important points about limitations of the<br>
zippered repository:<br>
<br>
<a href="http://lists.llvm.org/pipermail/llvm-dev/2018-November/127460.html" rel="noreferrer" target="_blank">http://lists.llvm.org/pipermail/llvm-dev/2018-November/127460.html</a><br>
<br>
git-bisect being more complicated is a deal-breaker for me. Checking<br>
out a random commit and only getting part of the project is just odd.<br>
<br>
-David<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div>
</div></blockquote><blockquote type="cite"><div dir="ltr"><span>_______________________________________________</span><br><span>LLVM Developers mailing list</span><br><span><a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a></span><br><span><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a></span><br></div></blockquote></body></html>