Re: [PROPOSAL] Remove proxy.config.cache.http.compatibility.4-2-0-fixup and code

2019-05-13 Thread Steven R. Feltner
+1 for cleaning out the old cruft! On 5/13/19, 8:32 PM, "Leif Hedstrom" wrote: This is an old feature, to make some migrations of way older versions and incompatible caches possible. I assume / hope that no one is running with this of an old cache any more? And, I believe even if you did,

Re: [PROPOSAL] Remove proxy.config.cache.http.compatibility.4-2-0-fixup and code

2019-05-13 Thread Sudheer Vinukonda
+1 > On May 13, 2019, at 8:50 AM, Leif Hedstrom wrote: > > This is an old feature, to make some migrations of way older versions and > incompatible caches possible. I assume / hope that no one is running with > this of an old cache any more? And, I believe even if you did, it would have > wra

Re: [PROPOSAL] Remove P_ or I_ naming convention for header files

2019-05-13 Thread Masaori Koshiba
> I’m pretty -1 on having files with the same filenames in different location. I’m sure that will just break all sort of shit, including my tiny brain. I strongly agree with this. > I’m leaning more towards Chao's proposal of cleaning up the actual mess. If we want to rename the I_ and P_ files, t

[PROPOSAL] Remove proxy.config.cache.http.compatibility.4-2-0-fixup and code

2019-05-13 Thread Leif Hedstrom
This is an old feature, to make some migrations of way older versions and incompatible caches possible. I assume / hope that no one is running with this of an old cache any more? And, I believe even if you did, it would have wrapped by now, such that this option is no longer needed. Let me know

Re: [PROPOSAL] Move from the IRC to Slack

2019-05-13 Thread Jason Kenny
+1 On Fri, May 10, 2019 at 6:46 PM Bryan Call wrote: > I would like to propose that we move from the IRC to Slack for IM > communication by June 1st. This is in response to ASF moving to Slack for > Infra and other channels and spamming that has happened on the IRC over the > last year. > > Thi

Re: [PROPOSAL] Remove P_ or I_ naming convention for header files

2019-05-13 Thread Leif Hedstrom
> On May 13, 2019, at 8:33 AM, Walt Karas > wrote: > > How about an approach using recursively nested modules? > - Exported headers for a module are in the module directory. > - Private headers and implementation (.cc) files are in a subdirectory > named "private". > - The submodules of a mod

Re: [PROPOSAL] Remove P_ or I_ naming convention for header files

2019-05-13 Thread Walt Karas
How about an approach using recursively nested modules? - Exported headers for a module are in the module directory. - Private headers and implementation (.cc) files are in a subdirectory named "private". - The submodules of a module are subdirectories of the module directory. - Module source files