+1 Netware
Justin Erenkrantz [EMAIL PROTECTED] Wednesday, November 17,
2004 1:37:33 PM
Can we please get some feedback on the following releases:
http://www.apache.org/~jerenkrantz/0.9.5/
(The directory actually contains 0.9.5 and 1.0.1.)
If we get 3 +1s, then I'll copy it over to dist. --
Hi,
I am looking for some simple logging API for C when I working on
jxta-c, and since log4c is under LGPL, I decided to start my own work
with a simple API. As discussed briefly in [EMAIL PROTECTED], I
thought it may be a nice-to-have for apr-util.
So, I post this here and apr-util is
--On Thursday, November 18, 2004 11:49 PM -0700 Paul Querna
[EMAIL PROTECTED] wrote:
Currently we have 'APR_0_9_BRANCH' and 'APU_0_9_BRANCH' as branch names
in subversion.
Is there any reason not to make these both '0.9.x'?
This is how httpd has been done, and both APR/APU have '1.0.x' branches.
On Thu, 18 Nov 2004 17:22:50 +0100, Uwe Zeisberger
[EMAIL PROTECTED] wrote:
Below comes a log and a patch. I assume, that apr_xlate_conv_buffer
should convert inbuf and assume, that the strings ends then. Else its
use in test/testxlate.c is not appropriate.
it was assumed that the application
On Nov 19, 2004, at 12:49 AM, Paul Querna wrote:
Currently we have 'APR_0_9_BRANCH' and 'APU_0_9_BRANCH' as branch names
in subversion.
Is there any reason not to make these both '0.9.x'?
This is how httpd has been done, and both APR/APU have '1.0.x'
branches.
I didn't want to just go do it now,
While playing around with the test suite on the way back from ApacheCon
I noticed that if you kill testall at just the wrong time it'll leave
stray shm sections around and further test runs will all fail. Here's a
patch and log message that removes shm sections proactively before
trying to
Brian W. Fitzpatrick wrote:
+1, but since 'svn log --stop-on-copy' will log backwards until the
start of this latest copy, it may be worthwhile to note in your log
message the initial revision where the branch was created (for purposes
of merging later. You can always get this information
In an attempt to see what happened in the last day or so while my email
was accidentally being routed to /dev/null (never mess with your email
settings right before getting on a plane, it's just asking for trouble)
I checked out the eyebrowse archives for dev@apr.apache.org and
[EMAIL
--On Friday, November 19, 2004 9:00 AM -0800 Garrett Rooney
[EMAIL PROTECTED] wrote:
Can someone either kick the thing until it works again or point me in the
direction of the right person to bug?
Eyebrowse is horribly broken. We want to re-create our archives on another
box, but that's going
On Fri, Nov 19, 2004 at 08:08:40AM -0800, Garrett Rooney wrote:
While playing around with the test suite on the way back from ApacheCon
I noticed that if you kill testall at just the wrong time it'll leave
stray shm sections around and further test runs will all fail. Here's a
patch and
Justin Erenkrantz wrote:
--On Friday, November 19, 2004 9:00 AM -0800 Garrett Rooney
[EMAIL PROTECTED] wrote:
Can someone either kick the thing until it works again or point me in the
direction of the right person to bug?
Eyebrowse is horribly broken. We want to re-create our archives on
Paul Querna wrote:
Joe Orton wrote:
Quite a lot of unnecessary whitespace changes, e.g:
I believe all of these changes are in accordance with the style guidelines.
I made style 'fixes' in the new files, and did the same with what is
left of poll.c. I guess I shouldn't treat the changed poll.c as
Now that we have converted to SVN, why doesn't the subject line
include the file that is being changed in the commit message? This
makes it harder to prioritize patches that need to be reviewed.
Brad
[EMAIL PROTECTED] Thursday, November 18, 2004 2:31:22 PM
Author: jorton
Date: Thu Nov 18
Hi Brad,
Now that we have converted to SVN, why doesn't the subject line
include the file that is being changed in the commit message? This
makes it harder to prioritize patches that need to be reviewed.
Even though I'm a newbie as far as SVN (and APR) are concerned, I
believe I can
At 12:04 PM 11/19/2004, Garrett Rooney wrote:
Second there is an awful lot of changing from foo *bar to foo * bar when
pointers are declared
foo * bar implies multiplication to the reader.
foo *bar implies pointer dereference.
Syntactically equal, visually very different.
At 12:30 PM 11/19/2004, Abbate, Joseph M wrote:
Hi Brad,
Now that we have converted to SVN, why doesn't the subject line
include the file that is being changed in the commit message? This
makes it harder to prioritize patches that need to be reviewed.
Even though I'm a newbie as far as
--On Friday, November 19, 2004 11:11 AM -0700 Brad Nicholes
[EMAIL PROTECTED] wrote:
Now that we have converted to SVN, why doesn't the subject line
include the file that is being changed in the commit message? This
makes it harder to prioritize patches that need to be reviewed.
Our CVS
Justin Erenkrantz wrote:
--On Friday, November 19, 2004 11:11 AM -0700 Brad Nicholes
[EMAIL PROTECTED] wrote:
Now that we have converted to SVN, why doesn't the subject line
include the file that is being changed in the commit message? This
makes it harder to prioritize patches that
I'm sure that last thing that you want to hear is another complaint
after all of the work you have gone to, but I'm not sure just listing
directories is a better compromise. At least before I could see the
difference between CHANGES and STATUS, now I just see trunk which
could be any one of a
--On Friday, November 19, 2004 2:41 PM -0700 Brad Nicholes
[EMAIL PROTECTED] wrote:
listings to keep the subject line shorter and more informative. I also
don't need to see svn commit: r at the front of every message. I
already know it is an SVN commit based on the mailing list it came
I understand about the revision numbers and I agree that it is an
important piece of information, but unnecessary on the subject line.
The subject line needs to include information that allows one to quickly
sort and prioritize the commits. IMHO, the revision number isn't a
piece of
Hi. I know Im
new, and I wanted to check out the APR-1.0.0 release. With the release, APR is receiving a lot
of attention at the moment, so I thought Id post my only problem and
solution.
Everything compiled fine under cygwin and redhat linux, but
choked in msdev. The .dsp and .dsw
Brad Nicholes wrote:
I'm sure that last thing that you want to hear is another complaint
after all of the work you have gone to, but I'm not sure just listing
directories is a better compromise. At least before I could see the
difference between CHANGES and STATUS, now I just see trunk which
Kris Carlgren wrote:
Hi. I know Im new, and I wanted to check out the APR-1.0.0 release.
With the release, APR is receiving a lot of attention at the moment, so
I thought Id post my only problem and solution.
Everything compiled fine under cygwin and redhat linux, but choked in
msdev.
24 matches
Mail list logo
