search for: unjust

Chandler Carruth via llvm-dev wrote: > However, it is incredibly > important to not expect or demand that a person *you have made feel > unsafe* take the time to explain why. I feel what you have written here to be offensive to the highest degree, and your words make me feel unsafe when contemplating their effect on my prospects for future interaction with this community.

...t;big-picture" task. My main question is this: how is the bounty divided? Does the person who does this "grunt work" get the whole $5,500, or does part of it go to the authors of t38modem/spandsp (which would surely be a large part of any solution)? I guess on one hand it would be unjust *not* to divide the bounty with them, but on the other hand, if the bounty is to be divided, I think the uncertainty about exactly how that would happen might be a factor in why the bounty has gone unclaimed for so long. - a -- PGP/GPG: 5C9F F366 C9CF 2145 E770 B1B8 EFB1 462D A146 C380

...n't consider my personal sense of being offended to constitute a valid counter argument.) > I don't think that he's saying that that person will *never* have to > explain, or that at least someone else could not explain. Nor he's > saying, IIUC, that this is an excuse for unjustly mistreating the > offender. We don't want excuses either way. We want resolve. > > I also felt that the wording reflected that, and why I raised the > issue in the first place. But I never thought Chandler or Tanya have > ever *meant* that, only that careful wording is in orde...

There is a new updated kernel for centos 3.1 that fixes a security issue. As I have not had time to test this build I am releasing it for testing for 24 hours to pick up any problems before general release. It is available at :- http://caos2.caosity.org:/centos/3.1/updates/i386/RPMS/ The version is 2.4.21-15.0.2.el.c0 Please install and test these packages, they are as yet unsigned and not

again, from here: http://wiki.centos.org/FAQ/CentOS5 regarding a newer version of PHP, a number of PHP experts that i know of suggest that, if you truly need an up-to-date version of PHP, you should: rpm -ivh http://rpms/famillecollet.com/enterprise/remi-release-5.rpm while remi collet's repo isn't official, it's accepted by numerous developers as a reliable source of newer PHP

Hi everyone, after attempting to correct Ivo's statement about Theora and Vorbis being the "default codecs" in the HTML 5 draft, I just got the following mail off list: "Why are you still here? And by here I mean the Xiph lists. I've seen you speaking ill of our formats and of free software more than in one occasion. So, for what purpose do you still stick around? What

...g, but I contacted the writer of an app I maintain in AppDB, to point out that his app runs perfectly under Linux and Wine. Straught away he modified his webpage to include the fact, and a link to the AppDB page for his application. Cheers, Ron. -- I prefer the most unjust peace to the most righteous war. -- Marcus Tullius Cicero -- http://www.olgiati-in-paraguay.org --

...use of social reasons. I have been battling social injustice my whole life (towards myself and others) because of my utter incompetence in understanding the social code (Autism), and this is one of the days that we all lose. I know this hasn't been an easy decision, and this is what makes it so unjust. Social pressure is real, and has real side effects. Let's discuss this off-list, I really think we can fix this. cheers, --renato

Please be patient and read this... Can AJ please change the license of the wine-launcher (like mono does)? You can still keep the libraries under LGPL. Please note proprietary is not bad and no oss w/o proprietary... You can make WINE a standard of binaries because of competition of Linux/BSD/Solaris binaries. It would be good for OS developers if you Change the license of the WINE launcher.

...ry version of R or compiled it yourself. <h3>Common posting mistakes</h3> Doing any of the following may result in you getting a response that you may find rude or insulting. (However, such a response may be justified in the eyes of some because you have wasted people's time or unjustly insulted people's work.) * Not doing your homework before posting a question. * Asking R-help to do your classroom homework for you (remember that many of the subscribers of R-help are university professors and can recognize homework questions with great speed and accuracy) * Claimin...

...monorepo. Is that right? lldb comes to mind, as it wasn't in > your list above. > > I understand that lldb is persona non grata in some circles. But. > It's not right to use the source code migration as a tool to revisit > an old decision like this. That is procedurally unjust. The relevant > decision should be, "is LLDB an LLVM subproject that is version-locked > to other subprojects, or not?” I really don’t want to debate LLDB. It is a hot issue for a lot of people, and I’d really prefer if we didn’t start a “let’s all rag on lldb” thread. Instead, let’s...

Hi all, I'm new to the forum. Oh no....newbie question coming, I hear you all cry! I'm playing around with Asterisk@home and have installed software and fiddled around with sip and extensions files. I have manage to make out going calls through Sipgate using X-Lite but cannot for some reason receive incoming calls. Incoming calls do not even show up on the switchboard panel. I've

...o mind, as it wasn't in >>> your list above. >>> >>> I understand that lldb is persona non grata in some circles. But. >>> It's not right to use the source code migration as a tool to revisit >>> an old decision like this. That is procedurally unjust. The relevant >>> decision should be, "is LLDB an LLVM subproject that is version-locked >>> to other subprojects, or not?” >> >> I really don’t want to debate LLDB. It is a hot issue for a lot of people, and I’d really prefer if we didn’t start a “let’s all rag...

This comes from Indymedia audio list, Whamb! should probobally be listed on the vorbis.com software pages. ----- Forwarded message from nathaniel t <vsea75@hotmail.com> ----- The whole world doesn't use Linux or Windows. Some tiny fraction of computer users use Macs. I didn't realize until yesterday evening how difficult and mysterious it is to try to listen to an icecast ogg

> On Jul 28, 2016, at 12:59 AM, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 28 Jul 2016 8:36 a.m., "David Chisnall via llvm-dev" <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > This does not apply to libc++. We support building the entire LLVM suite with other C++ standard library implementations (at

...ouncement number... * Blacklist/whitelist stuff: To blacklist the last caller... To blacklist this number... To whitelist the last caller... To whitelist this number... The last caller was... You have been blacklisted on this system. If you feel this is an error... If you feel this is in error, or unjust, please leave a message after the tone. Otherwise, please hang up now. Please stop calling. You are not welcome here. (once straight, and once mildly annoyed) "Due to the huge number of unsolicited calls we recieve, we are now screening all inbound calls where a caller ID is unavailable or...

...right? lldb comes to mind, as it wasn't in >> your list above. >> >> I understand that lldb is persona non grata in some circles. But. >> It's not right to use the source code migration as a tool to revisit >> an old decision like this. That is procedurally unjust. The relevant >> decision should be, "is LLDB an LLVM subproject that is version-locked >> to other subprojects, or not?” > > I really don’t want to debate LLDB. It is a hot issue for a lot of people, and I’d really prefer if we didn’t start a “let’s all rag on lldb” thread....

...o mind, as it wasn't in >>> your list above. >>> >>> I understand that lldb is persona non grata in some circles. But. >>> It's not right to use the source code migration as a tool to revisit >>> an old decision like this. That is procedurally unjust. The relevant >>> decision should be, "is LLDB an LLVM subproject that is version-locked >>> to other subprojects, or not?” >> >> I really don’t want to debate LLDB. It is a hot issue for a lot of people, and I’d really prefer if we didn’t start a “let’s all rag...

...right? lldb comes to mind, as it wasn't in >> your list above. >> >> I understand that lldb is persona non grata in some circles. But. >> It's not right to use the source code migration as a tool to revisit >> an old decision like this. That is procedurally unjust. The relevant >> decision should be, "is LLDB an LLVM subproject that is version-locked >> to other subprojects, or not?” >> >> >> I really don’t want to debate LLDB. It is a hot issue for a lot of people, >> and I’d really prefer if we didn’t start a “le...

Hi Duncan, > […] > 2. Those working on projects *outside* the monolithic repo will get the downsides of both: a monolithic repo that they are only using parts of, and multiple repos that are somehow version-locked. > > 3. For many (most?) developers, changing to a monolithic git repo is a *bigger* workflow change than switching to separate git repos. Many people (and at least some