search for: incentiving

Is Urguent any for the World and Messages of Expressivite,Communication at Hummanity,Society -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at

On Fri, Nov 16, 2012 at 1:53 PM, Greg Fitzgerald <garious at gmail.com> wrote: > My interpretations, which later in this long email, I'll assume as > premises to a recommended action: > > * Chris finds code reviewers to be exceptionally rare and the > community's most valuable participants. My previous "spork" > suggestion would be a decision made my

Many DI-related bugs are caused by missing Debug Location in an instruction created in a transformation. Most of the time the fix is trivial once you found where the culprit instruction is created (https://reviews.llvm.org/D50263). Currently, when you create a new Instruction, in order to give it DL you have to either use an IRBuilder that is previously set to the correct DL or “manually” create

LLVM Community, > http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-July/041738.html This was extraordinarily valuable in learning to understand the situation - thank you David Blaikie for pointing me to it. A few key snippets: "Because I optimize for the code reviewer, not the patch submitter," Chris Lattner "Forcing transitioning to git makes no sense for a lot of us - for

On Jul 23, 2019, at 9:17 AM, JF Bastien via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> On Jul 23, 2019, at 8:30 AM, James Y Knight via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> As a very frequent explorer of history, I really don't think this is >> as big an issue as it may seem. Even absent refactorings, you often >> run into the

Since the largest regional ILEC in Brazil completely stopped taking new BRI ISDN customers and started heavily incentiving their existing customers to migrate over to ADSL (regardless if what they need is voice or data), we have thousands of ISDN phones collecting dust. Is there any network side U cards that will work with Asterisk, so we can turn those phones into useful things ? I'm sure there will be expensi...

Warren Young wyml at etr-usa.com Tue Feb 3 00:32:15 UTC 2015 > Are you telling me you cannot memorize a series of 8 characters that do > not violate those rules? Keep in mind the original context isn't for production computers, it's testing Fedora. Many testers do dozens of installs per week, some do dozens per day. The password requirement is pretty annoying, I for one

Hi, I am sending my application I submitted for the GSoC. There are still some hours left before the deadline, so if you have any remarks or a tip, I can still update it. thanks... i think there are some grammatical errors =(... == Name and Contact details == Andr? Luiz Nazareth da Costa Primary e-mail: andre.lnc@gmail.com Secondary e-mail: andre.lnc@lsc.ic.unicamp.br Gtalk:

On Jul 29, 2019, at 10:58 AM, JF Bastien <jfbastien at apple.com> wrote: >> I think that Rui rolled this out in an incredibly great way with LLD, incorporating a lot of community feedback and discussion, and (as you say) this thread has accumulated many posts and a lot of discussion, so I don’t see the concern about lack of communication. > > I think there’s lack of proper

I am experiencing a curious event, and wondering if others have seen this... As well, I have a question related to it. Today, I noticed my puppet summary report from Foreman this morning, that 60 of my 160 hosts all stopped reporting at nearly the exact same time, and have not since restarted. Investigating, it appears that my puppetmaster temporarily ran out of disk space on the /var

On 6 Nov 2013, at 08:10, Renato Golin <renato.golin at linaro.org> wrote: > On 5 November 2013 10:12, <dag at cray.com> wrote: >> I'm fine with the general plan but I do want to see a longer notice >> period for toolchain changes on trunk. 1-2 months is too short. > > I may be wrong, but I think the final consensus was: for every new change, warn on (at

On 5 November 2013 10:12, <dag at cray.com> wrote: > I'm fine with the general plan but I do want to see a longer notice > period for toolchain changes on trunk. 1-2 months is too short. > I may be wrong, but I think the final consensus was: for every new change, warn on (at least) one previous release as when the changes go live. If I'm mistaken, this is still my

I see someone has noticed my lack of suggestions or recommendations for placement of virtual host source files... Since there are many places to put virtual host source files, I had intentionally avoided the discussion due to the complexities and to keep the document restricted to a single topic. I had planned to create a separate document devoted to the discussion. Specifically, there

As a very frequent explorer of history, I really don't think this is as big an issue as it may seem. Even absent refactorings, you often run into the "wrong" commit when looking at blame (e.g., someone just added a comma rather than actually changing the code you care about), and have to look past that, to another previous commit. Any interactive blame tool ought to have an easy way

[adding llvm-dev for wider audience] On Fri, May 19, 2017 at 12:28 PM, Daniel Berlin <dberlin at dberlin.org> wrote: > > > On Fri, May 19, 2017 at 11:00 AM, Davide Italiano <davide at freebsd.org> > wrote: > >> On Fri, May 19, 2017 at 10:00 AM, Sanjay Patel <spatel at rotateright.com> >> wrote: >> > Is "VRP" (value range

ANNOUNCING AGILE WEB DEVELOPMENT WITH RAILS, SECOND EDITION =========================================================== http://www.pragmaticprogrammer.com/titles/rails2/ Rails has changed a lot since we announced the first edition of the book a year ago. DHH says that the 1.1 release "boasts more than 500 fixes, tweaks, and features from more than 100 contributors." Who are we to

Hi all, Now that we're on GitHub, we can discuss about pull-requests. I'd like to propose to enable pull-request on GitHub, as a first step as an experimental channel alongside the existing methods for contributing to LLVM. This would allow to find workflow issues and address them, and also LLVM contributors in general to start getting familiar with pull-requests without committing to