How to contribute changes to Memcached 1.6

ode in the past. thanks, \rajiv

Re: How to contribute changes to Memcached 1.6

isclose any which may be in use in your changes. All our code is totally patent or otherwise un-encumbered and is intended to be released under Memcached's BSD (?) license. thanks, \rajiv On Wednesday, June 20, 2012 11:10:46 PM UTC-7, Dormando wrote: > Hey, > > Wow, that sounds

Re: How to contribute changes to Memcached 1.6

quiet different from the version I already had. For one - I don't see the bundled libevent? What I downloaded was: memcached-memcached-1.6.0-beta1-77-ge70f5ac.zip Just want to make sure I grabbed the right tree. thanks, \rajiv On Wednesday, June 20, 2012 11:10:46 PM UTC-7, Dormando wro

Re: How to contribute changes to Memcached 1.6

OK I am going to do it the right way :) Question - are these the right steps to do this : 1. "Fork" the repository on GitHub 2. "Clone" the repository to my local machine 3. Make my changes to the code locally 4. "Push" the commits back to gitHub thanks, \rajiv

Re: How to contribute changes to Memcached 1.6

n/stable remotes/origin/stable-1.3 == Any clues woudl be much appreciated. thanks, \rajiv On Thursday, June 21, 2012 4:49:07 PM UTC-7, Dormando wrote: > That's a start, yes! > > but: > > 2.5: switch to engine-pu branch (afte

Re: How to contribute changes to Memcached 1.6

> git checkout -b rajiv origin/engine-pu > > On Sun, 24 Jun 2012, rajiv wrote: > > > I am having some git newbe trouble with the step 2.5: > > > > "2.5: switch to engine-pu branch (after cloning)" > > > >

Re: How to contribute changes to Memcached 1.6

/projs/mcd/memcached (origin/engine-pu) $ git checkout -b rajiv origin/engine-pu warning: refname 'origin/engine-pu' is ambiguous. warning: refname 'origin/engine-pu' is ambiguous. fatal: Ambiguous object name: 'origin/engine-pu'. rkapoor1@RKAPOOR1-MOBL4 /c/projs/mcd/memcac

Re: How to contribute changes to Memcached 1.6

Sure. I should be able to push a branch in a couple of days. Would love for someone other than me to give it a try :) thanks, \rajiv On Monday, June 25, 2012 10:46:19 PM UTC-7, Viks wrote: > Hi, > > Can I get this new build for testing. I would really really want to do > som

Re: How to contribute changes to Memcached 1.6

anch (bagLRU) to gitHub? thanks, \rajiv On Thursday, June 21, 2012 4:49:07 PM UTC-7, Dormando wrote: > That's a start, yes! > > but: > > 2.5: switch to engine-pu branch (after cloning) > 4: push back to your own branch > > are all of the details. > > On Thu, 2

Re: How to contribute changes to Memcached 1.6

accessing https://github.com/rajiv-kapoor/memcached/info/refs fatal: HTTP request failed rkapoor1@RKAPOOR1-MOBL4 /c/projs/mcd/memcached (bagLRU) = thanks, \rajiv On Wednesday, June 27, 2012 11:19:26 PM UTC-7, rajiv wrote: > > push back to your own branch > OK I have

Re: How to contribute changes to Memcached 1.6

OK it worked this morning and the branch has been pushed as "bagLRU" thanks, \rajiv On Thursday, June 28, 2012 8:09:54 AM UTC-7, rajiv wrote: > > I tried: > > git push origin bagLRU > > but it did not do anything - just sat there forever. > > Actually fina

New optimized engine for Memecached 1.6

Hi, For anyone interested, I just posted a new 1.6 branch called "bagLRU" at * https://github.com/rajiv-kapoor/memcached/tree/bagLRU*<https://github.com/rajiv-kapoor/memcached/tree/bagLRU>that includes an optimized engine called “bag_lru_engine”. The Bag LRU engine im

Re: How to contribute changes to Memcached 1.6

The bagLRU engine is now available. Please see the other post about this. Do let me know if you have any questions or issues. thanks, \rajiv On Monday, June 25, 2012 10:46:19 PM UTC-7, Viks wrote: > Hi, > > Can I get this new build for testing. I would really really want to d

Re: How to contribute changes to Memcached 1.6

implementation, passing unit tests, code review by original authors, etc. etc. thanks, \rajiv On Wednesday, June 20, 2012 11:10:46 PM UTC-7, Dormando wrote: > Hey, > > Wow, that sounds neat! I was hoping to bum some free hardware from intel > so I could continue optimizing

Re: New optimized engine for Memecached 1.6

/home/memcached/.libs/bag_lru_engine.so" option when launching memcached. Hope that clears it up. thanks, \rajiv On Monday, July 2, 2012 4:59:49 PM UTC-7, p4 guru wrote: > Hi rajiv > > Could you elaborate on how to use Bag LRU, not sure what you mean by use > -E path to

Re: How to contribute changes to Memcached 1.6

Hi, You can find it at: https://github.com/rajiv-kapoor/memcached/tree/bagLRU Let me know if you have any problems. thanks, \rajiv On Sunday, October 7, 2012 6:05:02 PM UTC-7, 连海东 wrote: > Hi rajiv: > > I didn't find the badLRU branch on 1.6 repo, where can I g

Problem in installing Memcache in linux( RHEL)

collect2: ld returned 1 exit status make[2]: *** [memcached-debug] Error 1 make[2]: Leaving directory `/root/memcached-1.4.1' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/memcached-1.4.1' make: *** [all] Error 2 Regards Rajiv