Comment #4 on issue 215 by zohaib.h...@gmail.com: Source code ( a joke
probably )
http://code.google.com/p/memcached/issues/detail?id=215
it wont compile if you don't remove static and I discovered it when I got
compile error last night. So may be ignoring it is a bad idea.
Who's the owner of the Perl client library these days?
Should the rt.cpan.org tickets go somewhere else (somehow)?
-- Forwarded message --
From: Jan 'Yenya' Kasprzak via RT bug-cache-memcac...@rt.cpan.org
Date: Wed, Aug 10, 2011 at 6:47 AM
Subject: [rt.cpan.org #28095] [PATCH]
I deal with it when I have time...
...but I don't usually see that bug tracker, so it's easily forgotten.
Won't have time for a week or two, but I can kill some of those bugs,
though someone else is welcome to try as well. If you do though, please
actually test the fixes and ensure they won't do
Hey folks,
I'm a few days late, but here goes 1.4.7-rc1:
http://code.google.com/p/memcached/wiki/ReleaseNotes147rc1
I'm probably going to leave this up for a full week before cutting -final.
*please* test it with all of your might.
Now that we've cleared most of the open bug reports, perhaps
Comment #1 on issue 216 by zohaib.h...@gmail.com: Compile errors in
variables
http://code.google.com/p/memcached/issues/detail?id=216
I've tried to fix these errors and in pursuit of fixing chain of errors
here is the patch I have landed on.
I still don't know what to pass as first
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 216 by zohaib.h...@gmail.com: Compile errors in variables
http://code.google.com/p/memcached/issues/detail?id=216
What steps will reproduce the problem?
1. Open config_static.h
2. Add #define FUTURE at line 132 to enable
Comment #2 on issue 216 by trond.no...@gmail.com: Compile errors in
variables
http://code.google.com/p/memcached/issues/detail?id=216
The #define FUTURE stuff isn't complete, nor is it expected to work
There is another thread about _nuking_ the cachedump feature, so we won't
do any
