search for: l25

Displaying 9 results from an estimated 9 matches for "l25".

Did you mean: 25
2000 Mar 31
1
R: one bananna aov() question
...3 L17 8 -2.28559322033898 34 L18 9 -3.78559322033898 35 L19 10 0.714406779661017 36 L21 13 -2.51016949152542 37 L22 14 0.489830508474576 38 L23 15 -2.03135593220339 39 L24 16 0.489830508474576 40 L25 17 0.489830508474576 41 L27 18 3.98983050847458 42 L28 19 0.489830508474576 43 L29 20 -3.51016949152542 44 L30 22 0.489830508474576 45 L1 1 -0.272561715904491 46 L2 11 -1.71489275596924 47 L3...
2007 Sep 24
0
[LLVMdev] RM Build
.../tmp/ccYAgFFY.s:85: Error: no such instruction: `ldr pc,[sp],' /tmp/ccYAgFFY.s:91: Error: junk at end of line, first unrecognized character is `@' /tmp/ccYAgFFY.s:92: Error: junk at end of line, first unrecognized character is `@' /tmp/ccYAgFFY.s:93: Error: no such instruction: `ldr r3,.L25' /tmp/ccYAgFFY.s:94: Error: expecting operand after ','; got nothing /tmp/ccYAgFFY.s:95: Error: invalid char '[' beginning operand 2 `[sp' /tmp/ccYAgFFY.s:96: Error: no such instruction: `ldr r0,.L25+4' /tmp/ccYAgFFY.s:97: Error: no such instruction: `ldr r1,.L25+8'...
2008 Apr 22
1
''dependencies'' and RedCloth
...'redcloth'' true My question is this: do we change the dependencies macro to load rubygems when this happens, or do we ignore it and demand that the user explicitly require a library outside of the dependencies macro (see http://github.com/meekish/collective/tree/master/config/init.rb#L25 for an illustration)? James H. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/merb-devel/attachments/20080422/45b832e9/attachment.html
2018 Feb 07
2
nouveau 30bpp / deep color status
On Wed, Feb 07, 2018 at 06:28:42PM +0200, Ville Syrjälä wrote: > On Sun, Feb 04, 2018 at 06:50:45PM -0500, Ilia Mirkin wrote: > > In case anyone's curious about 30bpp framebuffer support, here's the > > current status: > > > > Kernel: > > > > Ben and I have switched the code to using a 256-based LUT for Kepler+, > > and I've also written a
2015 Mar 11
1
Sieve reject with ORIG-TO vs TO
Hi, The bounce message generated by the reject extension has what looks like a hard coded message prefix that comes before the configurable reason text: "Your message to <username> was automatically rejected:" In some cases, the <username> is NOT the original-to address, which can cause confusion to the sender or expose private aliasing data that some people might want to
2018 Feb 09
0
nouveau 30bpp / deep color status
...even want > to somehow try to enumerate the different modes and let userspace pick > the mode that best suits its needs. That's already the case -- NVIDIA actually has like 5 different LUT modes on recent chips. https://github.com/envytools/envytools/blob/master/rnndb/display/nv_evo.xml#L25 <value value="0x4" name="INTERPOLATE_1025_UNITY_RANGE" variants="GF119-"/> <value value="0x5" name="INTERPOLATE_1025_XRBIAS_RANGE" variants="GF119-"/> <value value="0x6" name="INTERPOLATE_1025_XVYCC_RANGE&quo...
2007 Sep 04
11
returning(...) ?
The following construct is an ActiveSupport-ism: returning(Foo.new) do |foo| ... end I don''t especially like it, since it''s both more verbose and less efficient than the direct alternative: foo = Foo.new ... foo It doesn''t occur many times in Merb, so does anyone agree with me that it should be removed? I tried doing this (patch attached) and I find
2017 Jul 31
2
Test Error Paths for Expected & ErrorOr
On Mon, Jul 31, 2017 at 8:19 AM Stefan Gränitz <stefan.graenitz at gmail.com> wrote: > Hi Lang, hi David, thanks for looking into this. > > > > Did you identify many cases where "real work" (in your example, the > nullptr dereference" was being done in an error branch? > > In my own code yes, not in LLVM ;) I'd like to run it on a large example,
2018 Dec 01
3
fixing debian's hd-media image
On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???