Displaying 10 results from an estimated 10 matches for "dippers".
Did you mean:
rippers
2012 Oct 16
2
List of Levels for all Factor variables
...uot;TCP1","TCP2": 2 1 2 2 2 1 1 2 1 2 ...
$ FLSASTATUS : Factor w/ 2 levels "E","N": 1 2 2 1 1 1 1 1 1 1 ...
$ MONTHLY_RT : int 17640 6932 5845 9809 11473 8719 19190 8986 7231 6758 ...
$ RETSTATUSDERIVED: Factor w/ 4 levels "401K","DOUBLE DIPPERS",..: 2 4 3 2 3 4 4 3 4 3 ...
$ ETHNIC_GRP_CD : Factor w/ 8 levels "AMIND","ASIAN",..: 8 8 8 8 8 8 8 8 8 8 ...
$ COMMUTE_BIN : Factor w/ 7 levels "","<15","15 - 24",..: 5 7 2 2 4 3 3 6 3 2 ...
$ EEO_CLASS : Factor w/ 4 levels &quo...
2006 Aug 09
7
changing find method
Hi,
i was wondering if there was a nice clean way(after all, it is ruby) to
change the find method of a certain model/class (Page) so that if i
wanted to use a find method on a @page instance it would return only
specific rows from the table(if the page.published == true/false:
the pages table looked like
SQL:
...
id int not null auto_increment,
published tinyint(1) not null,
something
2001 Mar 01
1
Bug report against openssh-2.3.0p1
I am writing to report a bug in openssh-2.3.0p1, and to suggest
a fix.
I have OpenSSH installed on a Solaris 8 box. The output of
uname -a is:
> SunOS dipper.csi.cam.ac.uk 5.8 Generic_108528-06 sun4u sparc SUNW,Ultra-5_10
OpenSSH was configured with the following options:
> ./configure --prefix=/jackdaw --with-default-path=/jackdaw/bin:/usr/bin
On this OS, with this configuration, it
2011 Dec 10
0
Announce: Puppet 2.7.9 Available
It seems like only yesterday that we were releasing Puppet 2.7.8.
But a day has passed and here is Puppet 2.7.9.
Puppet 2.7.9 is being released so shortly after Puppet 2.7.8 because it
introduced a regression on Ruby 1.8.5. The regression, issue #11306 would
cause a failure when handling non-empty recursive resources, such as a
recursive file resource.
The 1.8.5 incompatible code wasn’t caught
2011 Feb 22
1
ANNOUNCE: Puppet 2.6.5 - Release Candidate 5 available!
We''re back with a maintenance release: 2.6.5. This release addresses a
number of bugs in the 2.6.x branch and adds a handful of features and
documentation updates.
This release candidate contains fixes for bugs identified in the
previous release candidates:
- rc1 caused a warning on Ruby 1.8.6 which could cause log pollution. This
release candidate no longer generates the warning.
- rc1
2011 Feb 04
1
ANNOUNCE: Puppet 2.6.5 - Release Candidate 1 available!
We''re back with a maintenance release: 2.6.5. This
release addresses a number of bugs in the 2.6.x branch.
2.6.5 is a maintenance release in the 2.6.x branch and it contains only
bug fixes, documentation updates and a small handful of features.
The first release candidate is available for download at:
http://puppetlabs.com/downloads/puppet/puppet-2.6.5-rc1.tar.gz
We''re
2011 Feb 04
2
Fwd: [Puppet-dev] ANNOUNCE: Puppet 2.6.5 - Release Candidate 1 available!
----- Forwarded message from Nick Lewis <nick@puppetlabs.com> -----
Date: Thu, 3 Feb 2011 21:59:10 -0800
From: Nick Lewis <nick@puppetlabs.com>
To: puppet-users@googlegroups.com, puppet-dev@googlegroups.com
Subject: [Puppet-dev] ANNOUNCE: Puppet 2.6.5 - Release Candidate 1 available!
Message-ID: <AANLkTikjFwZ98P_NcxF54zHbU2mJf15XDrLg2cMp2GWT@mail.gmail.com>
We''re back
2012 Aug 30
0
[LLVMdev] Assert in LiveInterval update
Hi Sergei, Andy,
Sorry - I got distracted with some other work. I'm looking into this and
PR13719 now. I'll let you know what I find out.
Sergei - thanks very much for the investigation. That should help me pin
this down.
Cheers,
Lang.
On Tue, Aug 28, 2012 at 2:33 PM, Sergei Larin <slarin at codeaurora.org> wrote:
> Andy, Lang,
>
> Thanks for the suggestion.
>
2006 Dec 01
1
Packages build for Solaris ? As CSW packages ?
Well imitation is the highest form of flattery they say. So I''m surprised
to see these packages neatly built to install into /opt/csw correctly and
yet they exist somewhere else and have nothing to do with us here at
Blastwave.
fascinating.
I guess we can always send an email to the person doing this and just ask if
they want those packages in testing and then into the catalog for
2012 Aug 28
5
[LLVMdev] Assert in LiveInterval update
Andy, Lang,
Thanks for the suggestion.
I have spent more time with it today, and I do see some strange things in
liveness update. I am not at the actual cause yet, but here is what I got so
far:
I have the following live ranges when I start scheduling a region:
R2 = [0B,48r:0)[352r,416r:5)...
R3 = [0B,48r:0)[368r,416r:5)...
R4 = [0B,32r:0)[384r,416r:4)...
R5 = [0B,32r:0)[400r,416r:4)...