Re: [COMMITTERS] cvs commit: pgmemcache pgmemcache.c

2004-12-17 Thread Sean Chittenden
What I meant to write was, this commit message subject header is not using the pgfoundry format that was supposed to alleviate all concerns about flooding this list with messages that I am not interested in. Sorry about hijacking your message headers. I just committed a fix for that. I was goin

Re: [COMMITTERS] cvs commit: pgmemcache pgmemcache.c

2004-12-17 Thread Kris Jurka
What I meant to write was, this commit message subject header is not using the pgfoundry format that was supposed to alleviate all concerns about flooding this list with messages that I am not interested in. Kris Jurka ---(end of broadcast)--- T

Re: [COMMITTERS] cvs commit: pgmemcache pgmemcache.c

2004-12-17 Thread Kris Jurka
This commit message On Fri, 17 Dec 2004 [EMAIL PROTECTED] wrote: > seanc 2004/12/17 22:40:51 GMT > > PostgreSQL src repository > > Modified files: > .pgmemcache.c > Log: > *) Explicitly inline the macro wrappers for pfree(), palloc(), pstrdup(), > an

[COMMITTERS] cvs commit: pgmemcache pgmemcache.c

2004-12-17 Thread seanc
seanc 2004/12/17 22:40:51 GMT PostgreSQL src repository Modified files: .pgmemcache.c Log: *) Explicitly inline the macro wrappers for pfree(), palloc(), pstrdup(), and the homegrown pstrdup(). *) Have the MCM_CHECK() macro now check if the global