[llvm-dev] [cfe-dev] [6.0.0 Release] The release branch is here; trunk is now 7.0.0

Andrew Kelley via llvm-dev llvm-dev at lists.llvm.org
Thu Jan 11 08:38:48 PST 2018


Hi Hans,

I have a simple patch out for ReleaseNotes as well:
https://reviews.llvm.org/D41875

I do not have commit access.

Regards,
Andrew

On Wed, Jan 10, 2018 at 11:13 AM, Hans Wennborg via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> Hi Dan,
>
> You can commit it to ReleaseNotes.rst on the branch directly, or send
> me a patch or just some text and I'll do it for you.
>
> Thanks,
> Hans
>
> On Mon, Jan 8, 2018 at 8:31 AM, Dan Liew <dan at su-root.co.uk> wrote:
> > Hi Hans,
> >
> >> To get a change committed to the branch, first commit it to trunk as
> >> usual, and then request it to be merged --- ideally by filing a
> >> blocker bug on PR35804, or by cc'ing me on the commit email.
> >>
> >
> > What about adding a project to the list of projects ported to LLVM 6.0
> > in `docs/ReleaseNotes.rst`? I have a project that I've just ported to
> > LLVM 6.0 that I'd like to add to that list.
> >
> > It doesn't make a huge amount of sense to commit that to trunk because
> > that would suggest in the docs that the project is ported to LLVM 7.0.
> > This isn't the case right now and might not be the case in 6 months
> > time when LLVM 7.0 comes out.
> >
> >
> > Thanks,
> > Dan.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180111/f7e67887/attachment.html>


More information about the llvm-dev mailing list