In addition to the issues mentioned in this thread, I'd also like to ask if
it would be possible to fix these two bugs as well:
https://bugs.llvm.org/show_bug.cgi?id=43604 (maybe unique to Debian
packages)
https://bugs.llvm.org/show_bug.cgi?id=46321
Both of these are fixable exclusively by passing
+1, i'm just glad you're making progress on a promising option!
On Sat, Dec 28, 2019 at 8:33 PM JF Bastien wrote:
> The guy on the phone said that wouldn’t be a problem 🤷♂️
> I hope that stays correct! Ideally we’d have the same deal: indeterminate
> number of people, ordering off the menu. I’l
Mostly worried because we talked to them before and they wanted us to buy a
banquet menu at A lot of dollars.
On Sat, Dec 28, 2019, 19:15 JF Bastien via cfe-dev
wrote:
> I reached out to Steins (which is right across the street) to see if they
> can host us. I’ll keep y’all posted, it seeme
Hello folks,
I sent the message quoted below to llvm-dev@ just now, but it applies to
the whole community so sending an FYI here. Probably best to follow up w/
discussion on llvm-dev.
The archive link for reference is here:
http://lists.llvm.org/pipermail/llvm-dev/2019-November/136880.html
On Su
Thanks for your patience everyone, it was a bit rocky but got done.
The new license is in place and all subsequent contributions to LLVM
projects need to be under this license.
A couple of brief reminders to everyone:
1) For the next week or two, if you are submitting a patch on behalf
of someon
Ok, most of the prep work is done, and SVN access is going down now.
(Took us longer than anticipated, sorry about that.)
On Fri, Jan 18, 2019 at 2:52 PM Chandler Carruth wrote:
>
> We're getting the last things in place, and expect in roughly one hour
> we will pause all commit access while we p
We're getting the last things in place, and expect in roughly one hour
we will pause all commit access while we put in place the various
mechanical pieces of this.
I will send a somewhat detailed email reminding people of what has
changed when everything opens back up.
If this takes us more than
Greetings all!
# Summary
- We will put the new LLVM license and developer policy in place for all
subsequent commits next Friday (2019-01-18).
- Commit access will be stopped while this is done (starting 3pm PST,
hopefully under 3 hours).
- We will restore commit access for everyone covered by rel
I wanted to send out a general but brief update on relicensing as holiday
season (at least in my part of the world) approaches.
(If you don't know what the relicensing effort is, or want background, see
our website: http://llvm.org/foundation/relicensing/)
First off, a huge thank you to everyone
On Tue, Oct 16, 2018 at 4:51 PM Pavan Maddamsetti <
pavan.maddamse...@gmail.com> wrote:
> Dear LLVM community,
>
> Please do not agree to relicense LLVM under the Apache 2 license.
>
This has already been discussed extensively. Please see the posts I cited.
I don't really want to re-discuss this,
Greetings,
I wanted to provide an update to all the LLVM project (including all of its
sub-projects) developers about the ongoing effort to relicense under LLVM
under a new, unified license.
TL;DR: It’s actually happening. If you are a contributor to LLVM, help us
out by filling out our form and
Looks like 3:1 for having the social on July 12th... George, want to
officially call it (after confirming we can move w/ our lovely restaurant)?
On Thu, Jun 14, 2018 at 2:38 PM Chandler Carruth
wrote:
> Twitter poll should be up:
> https://twitter.com/chandlerc1024/status/1007376443762880513
>
>
Twitter poll should be up:
https://twitter.com/chandlerc1024/status/1007376443762880513
(Why twitter? I'm lazy and know how to do it... and hey, I always love
getting more folks on my twitter ;])
On Thu, Jun 14, 2018 at 11:35 PM George Burgess IV via cfe-dev <
cfe-...@lists.llvm.org> wrote:
FWIW, I don't have really strong objections, but I'm honestly not a fan.
The reason is mostly that I think it is very late to make the change and
likely to mean most people are on holiday when the branch occurs. I
somewhat anticipate significantly more cherrypicks as a consequence. I'd
love for App
Never mind. The option doesn't work the way desired. I'll follow up with
Eric about other ideas to reduce spam.
On Fri, Apr 21, 2017 at 2:51 PM Chandler Carruth
wrote:
> Hoping this will at least reduce the spam starting to show up. Let me or
> Eric know if you hit any issues with this (we've no
Hoping this will at least reduce the spam starting to show up. Let me or
Eric know if you hit any issues with this (we've not tried it before).
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Nah, its fine. Would have been completely easy to throw the necessary
hardware at handling the load if I hadn't messed up the config. =]
On Fri, Feb 17, 2017 at 2:39 PM Andrew Kelley via llvm-dev <
llvm-...@lists.llvm.org> wrote:
> Ah, sorry about that. Maybe I should have linked to the mailing l
, 2017 at 1:37 PM Alex Bradbury via llvm-dev <
> llvm-...@lists.llvm.org> wrote:
>
> On 17 February 2017 at 19:23, Chandler Carruth via lldb-dev
> wrote:
> > https://news.ycombinator.com/item?id=13670458
> >
> > I'm restarting Phab with lots more cores / me
Have they come back? the instance appeared to reboot cleanly and the pages
are serving... I'll dig into this in a couple of hours when I can.
On Fri, Feb 17, 2017 at 1:37 PM Alex Bradbury via llvm-dev <
llvm-...@lists.llvm.org> wrote:
> On 17 February 2017 at 19:23, Chandler Carrut
https://news.ycombinator.com/item?id=13670458
I'm restarting Phab with lots more cores / memory. Hopefully back up and
fast soon.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
On Thu, Jun 30, 2016 at 12:18 PM C Bergström
wrote:
> So discussion has been beaten to death and based on your comments - it
> seems you anticipate strong support.
>
I think there has been explicit strong support on the threads.
> Is any (in)formal vote planned? Will this just get enacted, "wh
Hello folks,
As mentioned some time ago[1], we’ve had a long (looong) series of
discussions about establishing a code-of-conduct for the LLVM project as a
whole over on the llvm-dev thread and the http://reviews.llvm.org/D13741
code review.
The discussion has largely died down for some time,
On Tue, Jun 28, 2016 at 12:55 PM Chandler Carruth via cfe-dev <
cfe-...@lists.llvm.org> wrote:
> My 2 cents.
>
And just to be explicit, I 100% support the person doing the heroic work to
*make* our releases having the final say in how they are numbered. =]
On Tue, Jun 28, 2016 at 12:45 PM Rafael Espíndola
wrote:
> > I don't think this is as obvious as you might think it is. We can happily
> > drop the "major version equals bitcode compatibility" implicit promise
> if we
> > want, but it's been there for a while and will need some messaging as to
>
On Mon, Jun 27, 2016 at 3:38 PM Hans Wennborg via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> On Mon, Jun 27, 2016 at 3:29 PM, Chris Lattner wrote:
> > On Jun 27, 2016, at 8:26 AM, Hans Wennborg via llvm-dev <
> llvm-...@lists.llvm.org> wrote:
> >> That's what concerns me about going to the sche
On Sun, Jun 26, 2016 at 10:01 AM Xinliang David Li via cfe-dev <
cfe-...@lists.llvm.org> wrote:
> I also believe this is the simplest versioning scheme*. It eliminates all
> future debates on this topic (e.g, when to bump major version etc) and
> solves the problem once and for all -- which is an
On Tue, Jun 14, 2016 at 1:32 AM Richard Smith via cfe-dev <
cfe-...@lists.llvm.org> wrote:
> On Mon, Jun 13, 2016 at 5:03 PM, Hal Finkel via cfe-dev <
> cfe-...@lists.llvm.org> wrote:
>
>> - Original Message -
>> > From: "Hans Wennborg via cfe-dev"
>> > To: "llvm-dev" , "cfe-dev" <
>> cfe
On Mon, Jun 13, 2016 at 5:03 PM Hal Finkel via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> - Original Message -
> > From: "Hans Wennborg via cfe-dev"
> > To: "llvm-dev" , "cfe-dev" <
> cfe-...@lists.llvm.org>, "LLDB Dev" ,
> > "openmp-dev (openmp-...@lists.llvm.org)"
> > Cc: "r jordans"
(actually spelling lldb-dev correctly, sorry for the typo)
We'll be at Tied House as usual, starting on Thursday the 4th at 7pm!
If you can, help us plan and RSVP here: http://meetu.ps/2RN2C5
See everyone there!
-Chandler
___
lldb-dev mailing list
lldb
Location is Tied House as usual.
Feel free to follow and RSVP here:
http://www.meetup.com/LLVM-Bay-Area-Social/events/226284610/
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
It's the first thursday of the month, and like every month, we have a
social!
7pm at Tied House as usual.
http://www.meetup.com/LLVM-Bay-Area-Social/events/226134792/
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailma
Please see the llvm-dev thread here and direct all discussion there:
http://lists.llvm.org/pipermail/llvm-dev/2015-October/091218.html
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
The plan is as always:
7pm, The Tied House, Mountain View
Meetup link: http://www.meetup.com/LLVM-Bay-Area-Social/events/224479893/
See folks there!
-Chandler
PS: sorry for not sending an email at the start of th eweek, will try to do
that more regularly.
___
It's that time again! Sorry for the late reminder, but tomorrow is the
first Thursday of the month and we will once again be gathering at the Tied
House at 7pm! Come, Joon us to debate new IR constructs, crazy C++ features
and any and everything else LLVM!
The meetup link is:
http://www.meetup.com
34 matches
Mail list logo
