On Mon, Oct 16, 2000 at 03:59:56PM -0500, Karl Fogel wrote:
> Karl Fogel <email@example.com> writes:
> > Greg, can you take a look, or forward this report to whoever maintains
> > the time code? Thanks.
> By the way, may I lobby once again for an APR-specific bug-reporting
"again" ? dang. Either I missed it the first time, or I dropped the ball...
> address to be mentioned somewhere in the APR documentation (i.e., a
> file at the top level of the APR tree)?
> I feel silly sending the reports to you personally, Greg, but also
> feel weird sending them as Apache bug reports. After all, if APR is
> truly a separable library, then this has nothing to do with Apache.
> So I send them to you. :-)
Well, several issues here.
*) I don't mind you sending them to me AT ALL. No problem. However, I do
believe it would be nice to have a different forum. For example, I'm
leaving for London on Friday for ApacheCan + leisure. I'll be gone about
10 days. I seriously doubt that I'm going to have any connectivity this
time around (unlike Aus). How do APR problems get fixed?
IOW, sending them here is fine, but various circumstances could affect
the response time.
*) While APR is *designed* to be separable from Apache, it was decided a
long time ago to not actually do it until after the Apache 2.0 release.
Primarly, this was done for logistical and ease-of-distro purposes. Much
like we're releasing APR with SVN itself, Apache wanted to do the same.
In addition, keeping it in the same CVS repository was a large win.
*) The Apache bug database has several problems (for people using it, and
the developers themselves). In addition, it is more focused on end-user
issues than "coding" type stuff that we find with APR.
So... my recommended forum is the firstname.lastname@example.org mailing list itself.
It is not a problem for anybody to post problems there, as long as they
relate to *code*. (you will be chastised for httpd.conf config issues,
though :-) About the only warning is to clarify at the top of your email
that you are not subscribed to new-httpd and ask for a CC: of the response.
It has that stupid Reply-To munging that we (thankfully) got rid of here.
[ <rant hopeful-listener="brian"> it's totally bogus for issues like this...
how can somebody post a question and expect a reply if the default MUA
sends the reply to the Reply-To rather than the questioner? bogus in many
ways... </rant> ]
As a final backup to new-httpd is to send directly to email@example.com (Ryan
Bloom) who could be considered the lead for APR.
But again: except for my travel, I'll handle any APR issue that comes in my
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:11 2006