search for: exclusionari

Dear R Helpers: I have a data set where the unit of observation is country-year. I would like to generate a new data set based on some inclusionary (exclusionary) criteria. Here is an example of the type of data that I have. df<-data.frame(cbind("country"=c(rep("Angola", 9), rep("Burundi", 7), rep("Chad", 13)), "year"=c(1975:1983, 1989:1995,

Ogg Vorbis is mentioned in CNET's MP3 Insider newsletter. I'm sending this article and another one that takes more thorough look at internet music distribution (from the same newsletter). -------------------------------------------------------------------- MP3: IT'S NOT REALLY FREE There is a widespread illusion that the MP3 file format is not a proprietary codec. It'd be nice,

From: Richard Humphrey <rlhumphrey at gmail.com> > Thanks that did the trick Although nVidia does put people on the Freedomware "nv" driver, and it can handle multiple framebuffers for Xinerama, VIVO (video in, video out), etc..., the Standardware "nvidia" driver is far easier to deal with for single framebuffer (no Xinerama) multiple displays, VIVO, etc..., in

Hi, what is the agenda of this list? I was surprised to find out about an OpenSSH developers mailing list without the developers of OpenSSH knowing about this. Strange, Niels.

On Tue, Oct 13, 2015 at 08:20:33PM +0100, Renato Golin via llvm-dev wrote: > On 13 October 2015 at 19:30, Chandler Carruth <chandlerc at gmail.com> wrote: > > For some of the reasons we at least need to make it clear the scope: > > http://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community/ > > Seems like a very personal opinion, and most

Hi, To try to bring our wiki 'up to date' (as in, no longer talking about CVS), I've gone through and rewritten a lot of the wiki content for our main landing pages: our front page, the software and specifications pages, the infrastructure pages, and even (to an extent) the mission statement. A lot of this is trying to describe how we've interpreted these things over the past ten

WinXP, R-2.9.1 LS., I have been trying to solve a (for me) tricky issue. No matter what I've tried, I just can't find a way to do this. This is the issue: I have a text file (ansi text) "titles.txt" with lines of text; here is an example of such a file: >>>>> a brief history of polio vaccines anti-vaccination movements and their interpretations early warning

On Tue, Oct 13, 2015 at 11:16 AM Renato Golin <renato.golin at linaro.org> wrote: > On 13 October 2015 at 18:59, Chandler Carruth via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > We have *not* appointed any such committee at this point. > > (...) > > The appeal is to the board of the Foundation. I don't expect the board to > > *be* the committee

Greetings all, First off, thanks to everyone who contributed to the initial discussion thread. Judging by the responses from that thread, there seems to pretty broad interest in pursuing this. There also seem to be a few concerns. =] I'm including an updated draft based on the feedback, and I'll also try to break down the major points I've seen of discussion. Sorry for the long email,

Greetings everyone, On behalf of the board of the LLVM Foundation, I’d like to start the process of introducing a formal code of conduct for the community. For a long time, various members of the community have been enforcing basic reasonable and respectful behavior, but to an outsider this may not be obvious. A public code of conduct advertises the behavior we expect of community members and

Thanks @Robin and @Graham for giving some background on scalable vectors and clarifying some of the details! Apologies if I'm repeating things here, but it is probably good to emphasize the conceptually different, but complementary models for scalable vectors: 1. Vectors of unknown, but constant size throughout the program. 2. Vectors of changing size throughout the program. Where (2)

Am 13.10.2015 um 12:52 schrieb Renato Golin via llvm-dev: > On 13 October 2015 at 02:42, Chandler Carruth via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> On behalf of the board of the LLVM Foundation, I’d like to start the process >> of introducing a formal code of conduct for the community. > > Hi Chandler, > > I agree we need such guidelines, and I truly

> On Oct 13, 2015, at 2:45 PM, Philip Reames via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > +1 to the general idea of a CoC > > A couple of specific thoughts: > > 1) It would have been nice for this not to appeared out of thin air. In an ideal world, a previous update would have mentioned ongoing thought and research in this area. > Some back story here. I

On Sat, Oct 17, 2015 at 8:24 PM, Pasi Parviainen via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On 14.10.2015 23:36, Chandler Carruth via llvm-dev wrote: > >> * **Be welcoming.** We strive to be a community that welcomes and supports >> people of all backgrounds and identities. This includes, but is not >> limited >> to members of any race,

While I'm replying to Renato here, that is mostly because there are too many replies on this subject, and too many of them have wandered off into other topics. I want to specifically address the concerns with verbosity. For example: On Tue, Oct 13, 2015 at 3:52 AM Renato Golin <renato.golin at linaro.org> wrote: > I also agree that some descriptions are too verbose, and trying to

I hope no one gets offended by my asking, but I wonder what others think about the possibility of splitting the list into two or three focal areas. Personally, I think I''d like to see three seperate lists: 1) newbie development (e.g., help working through tutorials, etc.) 2) more advanced development topics, 3) environment setup / admin.. What do you think? Best regards, Bill

Hi Luke, > was it intentional to leave out both jacob and myself? > [...] > if that was a misunderstanding or an oversight i apologise for raising it. It was definitely not my intention to be non-inclusive, my apologies if that seemed the case! > can i therefore recommend a change, here: > [...] > "This patch adds vscale as a symbolic constant to the IR, similar to >