<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font size="-1">Renato,</font></p>
<p><font size="-1">By your earlier requirements for tier 1, not
seeing how tier 2 could break tier 1. If a file was in tier 2,
it would not be in tier 1. There would be no action in tier 1 on
tier 2 files to cause a break.</font></p>
<p><font size="-1">What this may mean is that those working in tier
2 do not wander into tier 1, obscuring that distinction. Or that
there may be some confusion about what was in tier 1 vs. 2. That
in some manner the distinction becomes not well defined.<br>
</font></p>
<p><font size="-1">Neil Nelson<br>
</font></p>
<div class="moz-cite-prefix"><font size="-1">On 10/30/20 6:13 PM,
Renato Golin via llvm-dev wrote:<br>
</font></div>
<blockquote type="cite"
cite="mid:CAPH-gff7nKxJyLZWQDkmG-6CrP_4_SSJ_QjbiXMYtt5DMBCMNA@mail.gmail.com"><font
size="-1">But I wanted to express: "3 can't break 2 can't break
1", and make it easier to drop silly scripts or config files if
they're no longer valid or maintained, more easily than dropping
entire build systems.</font></blockquote>
</body>
</html>