Fuck the freeze, just commit it. Nobody here has a right to freeze the
tree unless they intend to stay up all night working on it until it
can be unfrozen.
Roy
On Thu, May 10, 2001 at 11:12:04PM -0700, Dirk-Willem van Gulik wrote:
This fixes all warnings and bugs I know of on
On Fri, 11 May 2001, Stas Bekman wrote:
On Thu, 10 May 2001, Roy T. Fielding wrote:
* checked out httpd-2.0 from scratch and now it works. I suppose that
'make distclean' is not very clean, since with 'cvs up' + 'make distclean'
the error didn't go away.
You probably didn't
[EMAIL PROTECTED] writes:
fielding01/05/11 01:12:12
Modified:.CHANGES configure.in
Log:
Simplify the configuration process by moving all libtool stuff to APR
and moving the last bits of hints.m4 inline. Now we only run every
test four times instead of five.
[EMAIL PROTECTED] writes:
fielding01/05/11 01:12:12
Modified:.CHANGES configure.in
Log:
Simplify the configuration process by moving all libtool stuff to APR
and moving the last bits of hints.m4 inline. Now we only run every
test four times instead of five.
From: Dirk-Willem van Gulik [EMAIL PROTECTED]
Sent: Friday, May 11, 2001 1:12 AM
This fixes all warnings and bugs I know of on FreeBSD/MacOSX. Still
checking on Solaris; whilst trying to find out if we are in a freeze -
slow going - am traveling myself (it is cold, and here is thunder,
What he said [erm, I meant] ... no you are always welcome to put bug fixes into the
code regardless of the 'freeze' status. I mean, and meant, to propose we freeze any
new feature patches. I'll absolutely wait for dirk to re-sync ab to his tree.
From: Roy T. Fielding [EMAIL PROTECTED]
Sent:
William A. Rowe, Jr. wrote:
Let's drop the word freeze from our vocabulary, and use the phrase
feature-freeze so we stop having this silly discussion. We aren't agreed on
how to fork the code for maintenance, and until we come to a concensus, we
need to continue on the old way of doing
From: Jim Jagielski [EMAIL PROTECTED]
Sent: Friday, May 11, 2001 9:05 AM
William A. Rowe, Jr. wrote:
Let's drop the word freeze from our vocabulary, and use the phrase
feature-freeze so we stop having this silly discussion. We aren't agreed on
how to fork the code for maintenance, and
hi Graham.
is there a way to specify a incoming filter for a reverse proxy request in the current
config command
structure?
we intend and doing something similliar to what kwindla's patch does,
but were going to ad header lines based on a prefix of notes in the notes table
(ie .. add every
Ian Holsman wrote:
is there a way to specify a incoming filter for a reverse
proxy request in the current config command structure?
we intend and doing something similliar to what kwindla's patch does,
but were going to ad header lines based on a prefix of notes in the notes table
(ie ..
I wonder if no longer running the libtool configuration that time
keeps $GCC from being set at the point where we add -DAP_DEBUG (and
gcc-specific flags) for --enable-maintainer-mode.
Oooh, thanks for finding that one -- I noticed it last night but was
too tired to figure out what was
If at any time progress is stopped because someone committed a bad
patch to the tree, the best way to fix it is to revert the patch
(unless for some reason that patch is necessary for the release).
I'd say you can revert all of the changes for isnan and ab if you
are in a hurry to get this
Of course, last-minute bug fixes have also resulted in problems
that have required re-releases in short order. So yeah, maybe freeze
isn't a good term, but generally what we mean is we plan on
tagging and rolling soon and want to reduce the risk of
problems on the present code tree so we
[EMAIL PROTECTED] writes:
orlikowski01/05/11 12:44:47
Modified:buildrules.mk
..
Index: rules.mk
===
RCS file: /home/cvs/httpd-2.0/build/rules.mk,v
retrieving revision 1.54
retrieving revision 1.55
Hmmm? isnan/isfnf, while problematic, is a very appropriate patch since
it closes an opportunity for segfaults (even if they are caused by a third
party module, and not our code.)
I'd tend to agree on the ab patch, but it's here.
I'm preparing an alternate solution till those changes are all
Roy T. Fielding [EMAIL PROTECTED] writes:
BTW, not setting AP_DEBUG reveals millions of warnings due to the
typedef of cmd_func in http_config.h. I tried to fix that last night
but the code makes absolutely no sense to me. Somebody with hooks on
the brain needs to fix that.
ISTR that it
So which C compilers other than gcc have a -MM option which does the
right thing?
Prolly none. :)
However, this needs to be fixed anyway, so ...
I'll see what I can find.
Victor
--
Victor J. Orlikowski
==
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
On Thu, 10 May 2001, Luke Kenneth Casson Leighton wrote:
my concern is that apr_pool_join() is going to get in the way
or going to get very confusing.
well, i created it as part of debugging 1.3, it may make sense to
reformulate the debugging approach to APR memory. now that i'm convinced
Why are some AP_CORE_DECLARE and others AP_DECLARE? That doesn't make sense.
I was trying to use the correct macro for each of the modified
functions.
If I was in error, I'll be glad to fix it.
Victor
--
Victor J. Orlikowski
==
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL
-Original Message-
From: Greg Stein [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 11, 2001 2:42 PM
To: [EMAIL PROTECTED]
Subject: Re: cvs commit: httpd-2.0/server config.c
Why are some AP_CORE_DECLARE and others AP_DECLARE? That
doesn't make sense.
I'm not sure.
I've looked at
On Fri, 11 May 2001, Bill Stoddard wrote:
Hi all,
There has been some discussion on the proxy list about a patch that
allows request and response headers to be modified based on config
directives for proxy requests.
Ideally though, header fiddling should be done in mod_headers
Well since no one has commented, and I know how much everyone loves code
I'm going to go ahead and start implementing this in four phases:
1. Just update the data structures and minimal code to work with data
structure changes. No other code changes. This mostly amounts to
adding some
On Thu, May 10, 2001 at 08:37:38PM -0700, Roy T. Fielding wrote:
Yes, that is the standard reasonable default per the Gnu project's
makefile standards, which is why autoconf sets it. As you discovered,
it can be overridden by setting any value for CFLAGS prior to running
configure.
Should
* checked out httpd-2.0 from scratch and now it works. I suppose that
'make distclean' is not very clean, since with 'cvs up' + 'make distclean'
the error didn't go away.
You probably didn't update srclib/apr first. Any changes to the *.m4 or
*.in files won't work until both httpd-2.0 and
On Thu, 10 May 2001, Roy T. Fielding wrote:
* checked out httpd-2.0 from scratch and now it works. I suppose that
'make distclean' is not very clean, since with 'cvs up' + 'make distclean'
the error didn't go away.
You probably didn't update srclib/apr first. Any changes to the *.m4
Should the apr/configure.in prevent -O... options when it notes a -g?
Seems like it's an awkward reasonable default for debug / maintainer
mode.
I don't think it should default to anything, but then I am not Gnu.
I've never had any problems stepping through -O2 code, but that was
before all
26 matches
Mail list logo
