[llvm] r255302 - Clarify some of the wording on adding a new subcomponent to the

Eric Christopher via llvm-commits llvm-commits at lists.llvm.org
Thu Dec 10 14:32:38 PST 2015


On Thu, Dec 10, 2015 at 2:21 PM Rafael Espíndola <rafael.espindola at gmail.com>
wrote:

> >  * Including new things into the API: If an LLVM subcomponent has a C
> API already
> >  included, then expanding that C API is acceptable. Adding C API for
> subcomponents
> > -that don't currently have one is fine, and the details of how best to
> design that
> > -API should be discussed on the mailing list.
> > +that don't currently have one need to be discussed on the mailing list
> for design
> > +and maintainability feedback prior to implementation.
> >
>
> s/need/needs/ no?
>
>
>
Sure :)


> >  * Documentation: Any changes to the C API are required to be documented
> in the
> >  release notes so that it’s clear to external users who do not follow
> the project
>
> More non-ascii :-)
>
>
I think I've fixed it? I can't get a diff redoing it. If it's still there
after r255306 feel free to get it :\

-eric


> Cheers,
> Rafael
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20151210/4621f0fe/attachment.html>


More information about the llvm-commits mailing list