search for: flagrant

...ve Comparative Analysis. R Package > Version 1.2-0, > URL: http://cran.r-project.org/package=QCA > > This is just an encouragement, not a requirement, and the official citation > file meets the CRAN policies. Would that be acceptable? > At the very least, this is seems to be a flagrant violation of the *spirit* of the CRAN policy, which AFAIK is intended to enforce acknowledgement of the contributions of all copyright holders in the package. The fact that you are trying to bypass the policy by suggesting users use an unofficial citation which would not comply with the policy whil...

On Tue, Oct 6, 2015 at 4:58 PM, Adrian Du?a <dusa.adrian at unibuc.ro> wrote: > Hi Gabriel, > > On Tue, Oct 6, 2015 at 10:59 PM, Gabriel Becker <gmbecker at ucdavis.edu> > wrote: > >> [...] >> >> At the very least, this is seems to be a flagrant violation of the >> *spirit* of the CRAN policy, which AFAIK is intended to enforce >> acknowledgement of the contributions of all copyright holders in the >> package. The fact that you are trying to bypass the policy by suggesting >> users use an unofficial citation which w...

...sl" (a wrapper on their GPL library) should be published under a GPL-compatible license, being a derivative work (the FSF thinks so). Another question is if that "strict" interpretation of the GPL could be actually enforced, of course. Coming back to the GSL example, it seems a more flagrant violation of the license is already happening: http://www.numerit.com/gsl.htm (apparently the publisher of that product thinks that linking to a GPL dll doesn't impose any obligation to him, but the usual view of the FSF is quite the opposite; I just found that page by chance, I don't know...

...of the documentation with the source 3/ I have some experience with using doxygen for C++ code documentation and must warn you that there may be a need for some sacrifices; doxygen only does (quite poor) syntax analysis and is more C-suited; with certain C++ constructs, it fails quite flagrantly (at least the version I've used), an example being instantiation of a static object with global visibility scope, using constructor with arguments, e.g. something like this: MyClass my_var(arg1, arg2); doxygen misinterprets this as declaration of a function and requires you t...

...ntroller for "events" that belong to a specific user. I only want the creator to be able to edit or delete the event. I''ve got the proper foreign keys set up. I''ve finally arrived at the point where I can take baby steps with code, but looks like my first steps are in flagrant violation of the DRY principle. Here''s what I have so far in the "EventsController" and I know it''s ugly (but it works). def update @event = Event.find(params[:id]) if @event.user_id == session[:user] && @event.update_attributes(params[:event])...

Hi Gabriel, On Tue, Oct 6, 2015 at 10:59 PM, Gabriel Becker <gmbecker at ucdavis.edu> wrote: > [...] > > At the very least, this is seems to be a flagrant violation of the > *spirit* of the CRAN policy, which AFAIK is intended to enforce > acknowledgement of the contributions of all copyright holders in the > package. The fact that you are trying to bypass the policy by suggesting > users use an unofficial citation which would not comply...

It seems that /etc/locale.conf is ignored in Centos 7. As a traditionalist who prefers things sorted lexicographically rather than indiscriminately with case ignored and dates to be displayed in the form "Sep 11 2008", I have always added lines to this file: $ cat /etc/locale.conf LANG="en_US.UTF-8" # Fix collating sequence for sort and ls export LC_COLLATE=C #

...4:58 PM, Adrian Du?a <dusa.adrian at unibuc.ro> wrote: > > Hi Gabriel, > > > > On Tue, Oct 6, 2015 at 10:59 PM, Gabriel Becker <gmbecker at ucdavis.edu> > > wrote: > > > >> [...] > >> > >> At the very least, this is seems to be a flagrant violation of the > >> *spirit* of the CRAN policy, which AFAIK is intended to enforce > >> acknowledgement of the contributions of all copyright holders in the > >> package. The fact that you are trying to bypass the policy by suggesting > >> users use an unoffic...

Hi Samba wizards! Thanks in advance for your support! I am working on migrating an existing Samba 3.x PDC to new hardware, Samba 4.x and, eventually, LDAP. I'm finding out in the process that I don't understand it at all :-) Old configuration was 3.x as PDC, with tdbsam backend. Both NIS and winbind are running on the same server (as well as smb and nmb of course). Since I want the

On 12/2/2012 2:48 PM, Hal Finkel wrote: > > [...] As a result, we'll need to assign a unique identifier to each lifetime region (roughly a block in C99, although this may be only a partial block if a restrict pointer is declared in the middle of the block). Whether restricted pointer is declared in the middle of a block or not, does not matter from the standard's perspective.

...t;dusa.adrian at unibuc.ro> wrote: >>> Hi Gabriel, >>> >>> On Tue, Oct 6, 2015 at 10:59 PM, Gabriel Becker <gmbecker at ucdavis.edu> >>> wrote: >>> >>>> [...] >>>> >>>> At the very least, this is seems to be a flagrant violation of the >>>> *spirit* of the CRAN policy, which AFAIK is intended to enforce >>>> acknowledgement of the contributions of all copyright holders in the >>>> package. The fact that you are trying to bypass the policy by suggesting >>>> users us...

...esponses inline On Tue, Oct 6, 2015 at 1:58 PM, Adrian Du?a <dusa.adrian at unibuc.ro> wrote: > Hi Gabriel, > > On Tue, Oct 6, 2015 at 10:59 PM, Gabriel Becker <gmbecker at ucdavis.edu> > wrote: > >> [...] >> >> At the very least, this is seems to be a flagrant violation of the >> *spirit* of the CRAN policy, which AFAIK is intended to enforce >> acknowledgement of the contributions of all copyright holders in the >> package. The fact that you are trying to bypass the policy by suggesting >> users use an unofficial citation which w...

On Oct 5, 2015, at 6:31 PM, Uwe Ligges <ligges at statistik.tu-dortmund.de> wrote: > > > On 05.10.2015 23:47, Andrew Robinson wrote: >> As a fourth option, I wonder if the first author could fork the package? >> >> Presumably, appropriately cited, a fork is permitted by the license under >> which it was released. Then the original package, by both

Greetings, I thought this was supposed to be a list for educated people to discuss serious development of the ogg vorbis project. In light of that, it is amazing to see the level Mr. Segher Boessenkool drops down to in the last posts. More or less calling people insane and accusing them of being on crack and what not. I didn't want to post this on the list, for there is no reason to

I?m trying to spec a ?binary?, and as previously discussed on this list, I?m trying to do it ?from outside? ? i.e., by calling it with Kernel#` and observing the (side-)effects. Unfortunately, this doesn?t really let me spec expectations about its internals. Let?s assume I have a -d flag and I parse it with Trollop to set Conf.debug: opts = Trollop::options do opt :debug, ''Print debug

hi, after i test nsd i find the following. if i use this in a zone file: $ORIGIN example.com. CNAME www www CNAME x x A 1.2.3.4 then it's excepted by nsd what's more give the proper result. if the slave is nsd than there is no problem, while if the slave is bind i've got the following error:

Hello, I'd like to propose a new form of memory-aliasing metadata: scoped no-alias metadata. This can be used to model local 'restrict' pointers in C99, but should also be useful for other frontends (I think, for example, that Fortran will want this as well). Currently, we only use the restrict qualifier on function arguments in Clang where we translate the restrict qualifier as a

Friends, Romans, Countrymen, lend me your ears! Or, in this case, your eyes. It has become a problem I've noticed over and over again, that we tend to think the mailing list is some sort of forum, used to post whatever your hearts desire. This list, not unlike any other mailing list, has a purpose. A focus if you will. Hopefully this 'document' will point out some key things we

So, there are two primary ideas behind SSA form management in the loop optimizers of LLVM: - Require LCSSA form input, leverage its (very powerful) guarantees to simplify maintaining SSA form, and also maintain LCSSA form. - Don't bother with LCSSA form input, assume the worst, and use powerful incremental SSA formation utilities built on SSAUpdater to form SSA on demand when needed. (Note,