I will try that. But I do need to be a user which can commit into this repository. Sorry I never did anything like that in the past with Rivet.
On Fri, Nov 29, 2019 at 10:01 AM Massimo Manghi <mxman...@apache.org> wrote: > On 11/29/19 3:34 PM, Brice Hamon wrote: > > Hello Massimo, > > > > No problem at all. It was easy finally to recompile and start the apache > > in debug. > > Now I can do this I can troubleshoot anything. > > > > Sorry for not responding yesterday but I was off for Thanksgiving here. > > > > If you want I can do a real patch. Or even make a commit to a git > > repository if this is what you guys use. > > I have no idea how you guys collaboratively are working. > > > > Thank you, > > Brice. > > > > > > Start with a fresh git repository (see > https://tcl.apache.org/rivet/html/download.html) and then do your > changes. The default branch is 'master' and I think you can safely apply > your patch there, then commit and push the patch. > > I recommend you add a new function in mod_rivet_cache.c and > mod_rivet_cache.h > > Functions in this module have RivetCache_ as prefix. In the current > implementation the cache is an hash table whose pointer is stored in a > rivet_thread_interp* structure. This is the structure pointer passed to > almost every function in this module > > -- Massimo Manghi >
