You could define, by mistake, the as wi Define Macro, then, what will
happen ...
On 20-02-2015 15:09, Tom Browder wrote:
On Thu, Feb 19, 2015 at 2:08 PM, Tim Bannister is...@c8h10n4o2.org.uk wrote:
On 19 Feb 2015, at 13:02, Nick Gearls nickgea...@gmail.com wrote:
Wrong answer: mod_macro
On Feb 23, 2015 6:38 AM, Nick Gearls nickgea...@gmail.com wrote:
You could define, by mistake, the as wi Define Macro, then, what will
happen ...
Can you be more specific, please?
-Tom
On Mon, Feb 23, 2015 at 3:45 PM, Gregg Smith g...@gknw.net wrote:
Am I missing something? Did I miss a boatload of email where any firm
decision was made?
I don't think you have missed anything. I assume very few people have
any clue how it's integrated/used today. The last thing I have in my
Hi,
I've been stalling on the traditional windows build adding apreq because
I never saw any concrete decision on if we were going to add it to the
core libhttpd or keep it a separate library (libapreq) as it has been
for years. I've searched my inbox and looked over all the messages about
I still want to do that just lacking tuits
Sent from my iPhone
On Feb 23, 2015, at 3:56 PM, Eric Covener cove...@gmail.com wrote:
On Mon, Feb 23, 2015 at 3:45 PM, Gregg Smith g...@gknw.net wrote:
Am I missing something? Did I miss a boatload of email where any firm
decision was made?
What would this mean for mod_perl users? I, and I assume many
others(?), still use the perl glue part of libapreq in mod_perl
software.
I only just spotted this thread, and just wondered how such mod_perl
users will be affected, if at all.
On 24 February 2015 at 03:24, Joseph Schaefer
