From: Luca Barbato <lu_zero@gentoo.org>
To: Craig Andrews <candrews@gentoo.org>,
llvm@gentoo.org, gentoo-dev@lists.gentoo.org
Cc: gienah@gentoo.org, gentoo@holzke.net
Subject: [gentoo-dev] Re: How to handle ROC forks of llvm and clang
Date: Fri, 14 Dec 2018 21:21:57 +0100 [thread overview]
Message-ID: <25afbdcd-1fcd-f21a-b128-201ad198eb6d@gentoo.org> (raw)
In-Reply-To: <5d774dabaee69376e4780c076fb271a6@gentoo.org>
On 14/12/2018 21:00, Craig Andrews wrote:
> Since ROC will eventually upstream all of it's work, (2) is ideal - but
> I have no idea what the timeline on that upstreaming effort may be, and
> I can't find anything that gives a hint.
I'd rather go with 1 and update the deps once llvm upstream gets the
right support.
lu
next prev parent reply other threads:[~2018-12-14 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 20:00 [gentoo-dev] How to handle ROC forks of llvm and clang Craig Andrews
2018-12-14 20:21 ` Luca Barbato [this message]
2018-12-14 21:02 ` Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25afbdcd-1fcd-f21a-b128-201ad198eb6d@gentoo.org \
--to=lu_zero@gentoo.org \
--cc=candrews@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo@holzke.net \
--cc=gienah@gentoo.org \
--cc=llvm@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox