CVS is our tool for managing our development sources, not a way to
fetch releases. Users of CVS have to know that. If you don't want
surprises, stick to the release downloads, or read the dev lists.
We can't be cornered into losing development history because we can't
reorg our repository
I'd suggest that 2.0 is a branch, and 2.1 is HEAD until we're ready
to stabilize 2.1, then we make another branch, which (assuming we do
the even is stable thing, or is it odd...whatever) may be called the
2.2 branch and HEAD becomes 2.3. Or something like that. Or leave the
branch as 2.1 a
It seems that Apache's ap_unescape_url() can't handle %u style
URI-escaped Unicode string, hence Apache::Request cannot neighther,
while CGI.pm can.
Is this a known issue?
--
Tatsuhiko Miyagawa <[EMAIL PROTECTED]>
* Aaron Bannert wrote:
> You may want to look at the AGB_BEFORE_AAA_CHANGES tag I made
> just for this purpose. I don't believe any commits were made
> between that tag and the auth changes.
but the docs. I guess, it's better to back out them manually (and remove
the obs_* stuff etc.) I'm willin
torsdagen den 28 november 2002 20.55 skrev Aaron Bannert:
> You may want to look at the AGB_BEFORE_AAA_CHANGES tag I made
> just for this purpose. I don't believe any commits were made
> between that tag and the auth changes.
So we might see v2.0.44 tomorrow then? ;)
I really hope so.
--
Regard
You may want to look at the AGB_BEFORE_AAA_CHANGES tag I made
just for this purpose. I don't believe any commits were made
between that tag and the auth changes.
-aaron
On Wednesday, November 27, 2002, at 04:28 PM, Sander Striker wrote:
Hi,
I'm swamped this week (big surprise...).
However, I
On Wed, Nov 27, 2002 at 11:29:36AM -0600, William A. Rowe, Jr. wrote:
> Francis, to the extent you don't want to reinvent the wheel;
>
> http://cvs.apache.org/viewcvs/apache-1.3/src/modules/standard/mod_autoindex.c
>
> should help you find that patch. Because 2.0 split before the feature
> was a
