Displaying 3 results from an estimated 3 matches for "4f3e1e00".
2016 Jul 29
0
Target Acceptance Policy
On 29 July 2016 at 18:01, Eli Bendersky <eliben at google.com> wrote:
> I don't know what the right number should be, to be honest. 2-3 sounds
> better than 6, though, given the rate of change of the LLVM codebase.
Good, that's the current version:
5. The target must have been stable in the tree and have addressed
every other minimum requirement for at least 2-3 months. This
2016 Jul 29
2
Target Acceptance Policy
...at the back-end and the target community can
> endure continuous upstream development for the foreseeable future.
>
> cheers,
> --renato
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160729/4f3e1e00/attachment.html>
2016 Jul 29
2
Target Acceptance Policy
On Fri, Jul 29, 2016 at 10:00 AM, Renato Golin <renato.golin at linaro.org>
wrote:
> On 29 July 2016 at 17:50, Eli Bendersky <eliben at google.com> wrote:
> > While I think the 6-month mark is artificial (what's wrong about a vague
> > "several months"? these are policies/guidelines, not legal contracts),
>
> I'm ok with that, too.
>
>