> We don't document bugs.
Honest question: why not?
S
First of all, I'd like to apologize for how long phpdoc has been
frozen, I got unexpectedly really busy with work the first days and
then got sick for few days :|
Anyway. The merge is now over and phpdoc-en now validates again;
phpdoc is therefore officially unfrozen as of now \o/
Awesome, guys.
I suspect that your complaint will be the tipping point and these
"translations" will be removed in the next few days :)
Philip and I had dinner on Wed night, and we discussed this.
The point that seems to be bothering him is a toss-up between exactly
what this thread is about and killing off
I want to work on PHP Documentation. How can i do it? I need to
send email
to somebody, join some mailing list?
Voila!
http://php.net/dochowto
If you have any specific questions, we're (generally) a friendly
bunch, so feel free to ask.
S
Please find a patch for mysql_escape_string attached, I'd like to
commit so
people know which characters
are actually getting escaped, it took me a long time to figgure it
out :)
Awesome idea.
"a backslash before before characters"...
I'd move the depreciation note into the 'notes' section
For what it's worth, the PDO reference page is the result of taking
the existing OO doc approach and trying to include an introductory
tutorial within the only logical spot.
In Dan's defense, it was also groundbreaking, as one of the first
documented OO extensions/sections.
S
How come there isn't any documentation for the new mysql_set_charset
function?
Nobody's written it yet.
Note your use of the word "new."
http://php.net/dochowto
Send a patch (-:
S
Yes, please! ;)
+1 from me, too
> Makes sense. As I was looking for PHP coding guidelines that lead to this
> page, I misunderstood the intend (which isn't clearly specified).
Here are some generally-accepted PHP style guidelines:
http://pear.php.net/manual/en/standards.php
S
As everyone may or may not have noticed, doc.php.net now points to pb11.
> btw, the phpweb rsync isn't probably working as this page is broken:
> http://doc.php.net.phpdoc.info/php/orphan_notes.php
Fixed. This was a permissions problem
So, I think everything is working now.
Cronjobs were juggled
> Please finish up POSIX and when it looks good we'll move towards getting
> you karma. In your CVS request* you might then say "To work on the
> documentation, I already created patches that were accepted for the
> POSIX extension."
IMO, request karma now, but please continue to submit patches to
seanMon Apr 16 02:01:38 2007 UTC
Modified files:
/phpdoc/entitiesglobal.ent
Log:
fix APD link
http://cvs.php.net/viewvc.cgi/phpdoc/entities/global.ent?r1=1.290&r2=1.291&diff_format=u
Index: phpdoc/entities/global.ent
diff -u phpdoc/entities/global.ent:1.
Hi All,
We've finally finished the move and sync of everything to pb11 for
docweb (see http://doc.php.net.phpdoc.info/).
Everything seems to be working. Please test that everything matches
doc.php.net.
Note: because of the domain difference, anything related to the MAGIC
cookie isn't going to wo
> - Whitespace is always one space, not two
Except in examples. Then use the pear standards:
http://pear.php.net/manual/en/standards.php
S
> Somebody has deleted all templates in xsl/ and no history left. When I
> was writing my previous letter they were there. That bloody CVS is no
> more useful than plain FTP if I constantly need to use mail list and
> archives to get the idea of "what the heck is going on"? FTP at least
> works thr
Martin Samesch wrote:
> Hi,
>
> grep -ri ' a [aeiou]'... gets a lot of hits. Should they be
> corrected or not?
Most of these are hard-vowel sounds, so "a user" (for example) is correct.
I see a few places where there are mistakes ("a Apache" for example),
though, and yes, those should be fixed.
seanSat Mar 3 18:24:01 2007 UTC
Modified files:
/phpdoc/en/reference/filesystem/functions fwrite.xml
Log:
add note about atomic fwrites in append mode
http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/filesystem/functions/fwrite.xml?r1=1.14&r2=1.15&diff_f
seanSat Mar 3 02:17:59 2007 UTC
Modified files:
/phpdoc/en/reference/apc/functions apc-define-constants.xml
Log:
tyop
http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/apc/functions/apc-define-constants.xml?r1=1.3&r2=1.4&diff_format=u
Index: phpdoc/en/refe
seanSat Mar 3 02:10:26 2007 UTC
Modified files:
/phpdoc/en/reference/apc/functions apc-define-constants.xml
Log:
concede and link to hidef
http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/apc/functions/apc-define-constants.xml?r1=1.2&r2=1.3&diff_format=u
seanSat Mar 3 01:17:35 2007 UTC
Added files:
/phpdoc/en/reference/apc/functions apc-add.xml
Modified files:
/phpdoc/en/reference/apc/functions apc-store.xml
Log:
apc_add
http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/apc/functi
Ruud Steltenpool, http://svg.startpagina.nl wrote:
> If the signature of the PHP4 version of a function is different than the
> PHP5 version i have to find that among a number of notes a bit down in
> the docs.
>
> I think it would improve read- and searchability a lot if you would just
> show the
> an optional parameter has been added to Phar::canCompress() as of
> 1.0.0RC2, is there any objection if I simply add the documentation, and
> don't put in a changelog for the method? 1.0.0RC1 was released today,
> and RC2 will follow in a few days, so it won't likely confuse users (the
> manual
,7 +15,7 @@
+--+
| Authors: Sean Coates <[EMAIL PROTECTED]> |
+--+
-$Id: functable.php,v 1.12 2007/02/06 06:32:56 sean Exp $
+$Id: functable.php,v 1.13 2007/02/06 07:11:06 sean Exp $
*/
// direct the
> Can someone point me at a pecl release that's missing protos--I'll fix
> it (if it's broken, which it probably is).
FWIW, classkit_import() is a good example of this.
(note that multiple PECL packages with the same function are supported)
Think I'll rebuild my whole database tonight (if I eve
,7 +15,7 @@
+--+
| Authors: Sean Coates <[EMAIL PROTECTED]> |
+--+
-$Id: functable.php,v 1.11 2007/02/06 05:36:24 sean Exp $
+$Id: functable.php,v 1.12 2007/02/06
>> This was already fixed in the English translation, so it's up
>> to the Germans to catch up (-:
On that note, Philip just said to me "i wonder if we can create a way to
store "important" items across translations, like for example,
deprecated status (ex. mysqli from that thread)"
After a bit
Sean Coates wrote:
> sean Tue Feb 6 05:36:24 2007 UTC
>
> Modified files:
> /phpdoc/scripts functable.php
> Log:
> parse source
Um. Sorry.
I may have been a bit premature in committing this.. I don't seem to
have a valid test case.
Ca
Hi,
> http://de3.php.net/manual/de/ref.mysqli.php
> MySQLi isn't experimental to the best of my knowledge. This was probably
> never removed.
This was already fixed in the English translation, so it's up to the
Germans to catch up (-:
S
/scripts/functable.php:1.10 phpdoc/scripts/functable.php:1.11
--- phpdoc/scripts/functable.php:1.10 Sun Feb 4 21:45:01 2007
+++ phpdoc/scripts/functable.phpTue Feb 6 05:36:24 2007
@@ -15,7 +15,7 @@
+--+
| Authors: Sea
Authors: Sean Coates <[EMAIL PROTECTED]> |
+--+
-$Id: functable.php,v 1.9 2007/02/04 21:41:57 sean Exp $
+$Id: functable.php,v 1.10 2007/02/04 21:45:01 sean Exp $
*/
// direct the output of
,7 +15,7 @@
+--+
| Authors: Sean Coates <[EMAIL PROTECTED]> |
+--+
-$Id: functable.php,v 1.8 2007/02/04 19:31:45 sean Exp $
+$Id: functable.php,v 1.9 2007/02/04 21:41:57 sean Exp $
*/
// direct
u phpdoc/scripts/functable.php:1.7 phpdoc/scripts/functable.php:1.8
--- phpdoc/scripts/functable.php:1.7Sat Feb 3 14:22:25 2007
+++ phpdoc/scripts/functable.phpSun Feb 4 19:31:45 2007
@@ -15,7 +15,7 @@
+--+
| Authors:
0 +15,10 @@
+--+
| Authors: Sean Coates <[EMAIL PROTECTED]> |
+--+
-$Id: functable.php,v 1.6 2007/02/03 12:07:21 bjori Exp $
+$Id: functable.php,v 1.7 2007/02/03 14:22:25 sean Exp $
*/
Authors: Sean Coates <[EMAIL PROTECTED]> |
+--+
-$Id: functable.php,v 1.4 2007/01/31 11:53:38 nlopess Exp $
+$Id: functable.php,v 1.5 2007/02/02 00:31:05 sean Exp $
*/
// direct the outpu
> no, because the files were moved, so when you checkout php-src you won't
> get the files. Only if you are considering adding "advanced pecl
> support" that will parse 'cvs log's of the pecl files and checkout each
> revision, but that seems too hardcore for now :)
That's what the script does for
Nuno Lopes wrote:
> just a side note: we should use museum.php.net instead of cvs to
> download older PHP releases, as cvs got history broken with some pecl
> moves.
What do you mean? Like when the files got physically moved from php-src
to pecl?
If so, once the script supports PECL, those tags s
Authors: Sean Coates <[EMAIL PROTECTED]> |
+--+
-$Id: functable.php,v 1.2 2007/01/31 03:43:11 sean Exp $
+$Id: functable.php,v 1.3 2007/01/31 04:00:25 sean Exp $
*/
-// direct the output of
15,9 +15,10 @@
+--+
| Authors:Sean Coates <[EMAIL PROTECTED]> |
+--+
+$Id: functable.php,v 1.2 2007/01/31 03:43:11 sean Exp $
*/
-// direct the output of this fine into phpdoc/phpbook/phpbook-xsl/versi
tely. |
+--+
| Authors:Sean Coates <[EMAIL PROTECTED]> |
+--+
*/
// direct the output of this fine into phpdoc/phpbo
Hi Jacques (and others),
An excerpt, for some context:
[20:33] i request you build the doc howto :)
...
[20:35] prometheus% ./howto
[20:35] autoconf: not found
[20:35] ./howto: ./configure: not found
[20:35] make: don't know how to make howtophp. Stop
[20:35] cp: howto/php/*: No such file or
seanTue Dec 19 22:00:01 2006 UTC
Modified files:
/phpdoc/en/reference/sessionini.xml
Log:
document handlers can be found in phpinfo()
http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/session/ini.xml?r1=1.44&r2=1.45&diff_format=u
Index: phpdoc/en/ref
Hi,
Replying to the list--it's a list question.
> I'm in the process of converting the UODBC extension dox to the new style.
>
> I have a 2 quick questions on the templates.
>
> 1 - In http://wiki.phpdoc.info/DocSkel/IniDotXml, should the tgroup
> cols value be 4 and not 3?
Yes, I think so.
>
Anyone know why the install.unix page would have you build apache with a
/www prefix?
This seems just wrong to me... either /usr/local/apache2 or /opt/apache2
(omit 2 if 1) seems more appropriate.
S
Hi all,
I've mentioned this on IRC, but it's now time to bring it over to the
list (I hope).
I've started rewriting functable; I've got a mostly-working version
written, entirely in PHP, so we can finally kiss that big blob of AWK
goodbye. No offense, but most of us have no idea how to maintain i
seanThu Oct 26 02:17:15 2006 UTC
Modified files:
/phpdoc/en/reference/filesystem/functions file-get-contents.xml
file-put-contents.xml
file.xml fopen.xml
Log:
ad
seanThu Oct 26 02:11:58 2006 UTC
Modified files:
/phpdoc/en/reference/filesystem/functions fopen.xml
Log:
zcontext is inconsistent with the rest of the manual
http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/filesystem/functions/fopen.xml?r1=1.27&r2=1.28&
seanSat Sep 30 18:20:02 2006 UTC
Modified files:
/phpdoc/en/reference/pcre/functions preg-replace.xml
Log:
bug #38999; fix language
http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/pcre/functions/preg-replace.xml?r1=1.17&r2=1.18&diff_format=u
Index: phpdoc/
seanWed Sep 20 03:37:27 2006 UTC
Modified files:
/phpdoc/en/reference/strings/functions explode.xml
Log:
change separator to delimiter to better match internal error messages
http://cvs.php.net/viewvc.cgi/phpdoc/en/reference/strings/functions/explode.xm
> There is a missing function from the ibm_db2 driver documentation. I would
> like to add this to the documentation package. This is my first try at
> this, I hope this is done correctly.
> If one of you kind folks can take a moment and add this to the
> documentation, it would be greatly apprec
Sean Coates wrote:
>> Extra, Extra, Read all about it... the exceptions role has officially
>> been renamed errors. Let the flood gates open!
>
> http://www.phpdoc.info/patches/massive-role-exceptions-errors.txt.gz
>
> Incoming bigass change..
>
> Please object by
> Extra, Extra, Read all about it... the exceptions role has officially
> been renamed errors. Let the flood gates open!
http://www.phpdoc.info/patches/massive-role-exceptions-errors.txt.gz
Incoming bigass change..
Please object by tomorrow (-:
( If I don't respond right away, it's because I'm
seanFri Sep 1 15:37:21 2006 UTC
Modified files:
/phpdoc/en/language operators.xml
Log:
WS
http://cvs.php.net/viewvc.cgi/phpdoc/en/language/operators.xml?r1=1.103&r2=1.104&diff_format=u
Index: phpdoc/en/language/operators.xml
diff -u phpdoc/en/language/opera
seanFri Sep 1 15:33:53 2006 UTC
Modified files:
/phpdoc/en/language operators.xml
Log:
note about non-obvious ternary evaluation (and recommend to avoid stacking);
bug #38679
http://cvs.php.net/viewvc.cgi/phpdoc/en/language/operators.xml?r1=1.102&r2=1.103&
> This is a proposal to rename 'exceptions' to 'errors' so it may cover,
> for example, when functions emit E_* level errors. Currently this
> information is either in the description, returnvalues, or notes roles
> but none of those are fully appropriate. Exception information would be
> put in
Olivier Hill wrote:
> On 8/22/06, Sean Coates <[EMAIL PROTECTED]> wrote:
>> Can you post it somewhere?
>
> XML DocBook Sources: http://www.olivierhill.ca/geoip-xml.tar.gz
I'm not concerned about grammar/spelling/etc. That stuff is easy to fix
later.
Looks good to me:
h
> IMHO you should keep it within the extension itself, phpdocs
> configure script has a --with-pecl-source=... option that will
> pick it up from PECL ...
PECL documentation has been stored in the phpdoc repository for a long
time now.
There are a few problems with putting the documentation in PE
> I will soon make a release for the PECL geoip module. As such, I have
> written documentation about the different functions and provided some
> code examples.
>
> Should I commit this to phpdoc? Everything is inside references/geoip.
> I have done a make test as well as test_xml, everything seem
seanSat Aug 12 20:14:32 2006 UTC
Modified files:
/phpdoc/en/appendices userlandnaming.xml
Log:
grammar and markup
http://cvs.php.net/viewvc.cgi/phpdoc/en/appendices/userlandnaming.xml?r1=1.1&r2=1.2&diff_format=u
Index: phpdoc/en/appendices/userlandnami
> Many functions return FALSE if something goes wrong/data has been
> exhausted/the function does not find what the developer was looking
> for.
>
> In fact, we'd have to mark a great number of functions in the manual
> "mixed" if we followed the convention you propose. Instead, we mark
> return v
seanThu Jul 27 20:59:29 2006 UTC
Added files:
/phpdoc/en/appendices userlandnaming.xml
Modified files:
/phpdoc manual.xml.in
/phpdoc/entitiesglobal.ent
Log:
Userland Naming guide -- from Lukas Smith
http://cvs.php.
anatoly techtonik wrote:
> ||*()*|| Hi, Nuno.
>
> I wonder if there is any link checker which runs once a month through
> documentation to catch all missing and/or outdated links?
> It can also save link contents with status 200, 302, "checked manually
> - ok" to detect when the pages are no longe
FYI, I just did:
bash-2.05b# rm -r /local/repository/phpdoc/ja /local/repository/phpdoc/kr
on y1, at Nuno/Philip's request -- these old directories were
conflicting with the phpdoc-ja, phpdoc-kr modules.
S
Michael Wallner wrote:
> Richard A. Quadling wrote:
>> The XML files are not well formed.
>>
>> You've got a leading space in front of the lines.
>>
>> Attempting to make the manual ...
>>
>> /cygdrive/D/cygwin/home/RichardQ/phpdoc/en/reference/http/HttpQueryStrin
>> g.xml:1: parser error : XML dec
> Since all appropriate functions will be unicode compatible in PHP 6.0.0
> this seems like information overload and not something that should be
> mentioned in every functions documentation. Perhaps have a list offsite,
> maybe on docweb, for alpha/beta testers.
Good point. I agree.
This list alr
Welcome,
> I just wanted to shoot a quick email to the list to see when we could
> start work on docs for Unicode upgrades (PHP 6). The main thing, IMO, is
> having a way to mark functions as Unicode compatible and also have a
> section (per-function) for any Unicode-related notes. Any other thoug
Ford, Mike wrote:
> On 05 July 2006 12:48, Nuno Lopes wrote:
>
>> No way
>>
>> We cannot start breaking translators' work. Anyway, what's
>> the problem with
>> contractions? When I studied English (British) I learned that
>> contractions weren't so formal, but they aren't wrong per se.
>>
>>
> So it's not clear to me that Ben is in the wrong here.
In any case, I un-volunteer to mess with >300 files on the CVS server.
S
>> I can just cvs remove the existing files and re-add them with their
>> lowercase names, but this will lose the history information attached to
>> the files? Is there another way you recommend I handle this?
>
> This will upset translators. (-:
>
> I can move the files in CVS.
>
> Translators:
> By the way, how do you recommend I go about this?
>
> I can just cvs remove the existing files and re-add them with their
> lowercase names, but this will lose the history information attached to
> the files? Is there another way you recommend I handle this?
This will upset translators. (-:
I
> +it can never be changed or undefined. Unlike functions, constants need to
> +be defined before they are referenced.
This isn't _necessarily_ true.
Example:
[EMAIL PROTECTED]:~$ php5 -r ' if (0) { function foo() { echo "foo"; } }
foo();'
Fatal error: Call to undefined function foo() in
Oliver Block wrote:
> I don't know, if you discussed on that lately/in the past but wouldn't it be
> a
> good idea, if pages that give an overview over the functions of an extension
> would be sorted differently?
I like the output, but this listing is currently generated by scripts,
so in order
Ben Ramsey wrote:
> I added the notes so that people reading the docs wouldn't get confused
> and assume that, since they are running PHP 5, they can use these new
> functions.
This is a logistical problem with docbook and OOP.
There's no actual simplexml_element_addAttribute() function, for examp
Philip Olson wrote:
> philipThu May 4 02:21:29 2006 UTC
>
> Modified files:
> /phpdoc/en/language types.xml
> Log:
> $str{42} isn't deprecated (yet?), but $str[42] is preferred. We'll mention
> that.
Deprecated != doesn't work (see dl())
I think t
> Thats why I've applied as mentor. I would like to mentor something about
> livedocs or the gcov.php.net site. (you can still apply as well)
FWIW, I'm also a mentor, and I'm available to help if anyone wants to
take/develop the livedocs project.
S
> The policy was to convert the pages to the "new" doc style, that doesn't
> use &listendand; at all.
Makes sense. That's why I asked. Thanks.
S
Hello.
Do we have a current policy on using &listendand; in See Also blocks?
S
Francesco Caccavella wrote:
> Hello, I'M Francesco Caccavella, content strategist for HTML.it, an
> italian site with a lot of documentation about web design.
>
> I would like to offer to my visitor the downloadable english and italian
> version of the PHP Documentation, without modification or ot
> ID: 35356
> It's not only limit and count, also array() syntax of $pattern and
> $subject should be mentioned.
>
> "See preg_replace() for description of other parameters."
Why not actually copy the descriptions to the preg_replace_callback page?
S
> How would you do that scan? Currently the entry/user-note.php script
> checks with a dns black-list that also includes zombie machines, but
> most seem that aren't detected.
Erm. I wrote up a quick script to check this, but failed to come up with
any hits, so I guess my theory is unsubstantiated
> The X-Spam-Status isn't always the same :) its almost the same.. I have
> already seen one different :) The spamassassin needs training to be
> useful to us.
Well, that may gain some accuracy, but I stand by my idea that
spamassassin will not work properly for notes because SA is designed to
han
Oops. Accidentally sent this to php-doc-chm
S
--- Begin Message ---
>
> Server IP: 194.109.193.119
> Probable Submitter: 80.56.58.248
>
> X-Spam-Status: No, hits=3.1 required=5.0 tests=DATE_MISSING,FROM_NO_LOWER
> autolearn=no version=2.64
>
What is the status of these mess
seanSun Mar 26 22:05:05 2006 UTC
Modified files:
/phpdoc/en/reference/apc/functions apc-cache-info.xml
apc-clear-cache.xml
Log:
describe clear_cache (param)
http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/apc/func
> Do we need to approve? I guess we have not enough "man-power" for that.
> Simply post the note after we receive the token.
That's what I meant. Note is approved when the token URL is clicked.
>> Max 5 notes per address per day. Or x notes per domain/IP per day..
>
> x notes per domain/IP per d
[resend: not sure why this didn't make it through, yesterday;
re-sending; sorry if it's a dupe -S]
Nuno Lopes wrote:
> Well we have already tried a couple of methods but none of them worked
> so far, including DNS blacklists, spamassassin and a simple words
> blacklisting.
> I've run out of ideas.
seanThu Mar 9 03:08:37 2006 UTC
Modified files:
/phpdoc/en language-snippets.ent
Log:
<\!-- Keep 'em sorted -->
http://cvs.php.net/viewcvs.cgi/phpdoc/en/language-snippets.ent?r1=1.162&r2=1.163&diff_format=u
Index: phpdoc/en/language-snippets.ent
diff -u ph
seanThu Mar 9 03:07:13 2006 UTC
Modified files:
/phpdoc/en language-snippets.ent
Log:
fix build; please expand on this
http://cvs.php.net/viewcvs.cgi/phpdoc/en/language-snippets.ent?r1=1.161&r2=1.162&diff_format=u
Index: phpdoc/en/language-snippets.ent
dif
> Please commit the entity for note.ob
Make that note.uses-ob
S
[EMAIL PROTECTED] wrote:
> /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/misc/functions/highlight-file.xml:28:18:E:
> character data is not allowed here
> /usr/bin/openjade:/dat/dev/php/phpdoc/en/reference/misc/functions/highlight-string.xml:28:18:E:
> character data is not allowed here
> /u
> PHP 5 uptake is also speeding up and there are a couple of areas of the
> manual that are confusing. A search for "xml" or going to php.net/xml
> lands you on php.net/manual/en/ref.xml.php which has no mention of the
> different xml implementations available.
The best way to handle this, probab
> The final decision will be of course up to you guys, but I would hope
> that the patch be applied. The patch would make the page a little too
> big, like you say, but I would vote for the consistency in page format
> (I don't see constants given as ranges elsewhere), than a slight page
> size in
> he probably has more time than Sean
Yes, I appreciate the thought, but I certainly don't consistently have
any extra time to devote to phpdoc -- sorry.
S
> It would be nice to do something about the tremendous amount of spam
> comments around phpdoc.info... Like:
>
> http://wiki.phpdoc.info/CurtZirzow?show_comments=1
Ew. what a mess.
I made the comment ACL to logged in users only (need @php.net to log
in), and I removed all comments that had "ht
> I did something like this in my quick tests:
Nevermind, I see you've got it under control.
S
> actually its not a config file, its a config dir :)
> I have many files in /usr/share/spamassassin, although not all are
> needed for us.
Ok.. what directives are you using? (-:
> Anyway, I think the best thing to do now is to implement a function to
> pass the note through spamassassin and dis
>> Piping user notes through spamassassin won't help--at least without some
>> special config that I don't know about.
>
> man spamassassin says:
> -C path, --configpath=path, --config-file=path
> Path to standard configuration dir
Cool. Out of curiosity, what do
> spam assasin is already there:
> /opt/ecelerity/3rdParty/bin/spamassassin -L -e 8
Piping user notes through spamassassin won't help--at least without some
special config that I don't know about.
For example, all notes would end up with headers like the following,
because they're not actually ma
>> Run the note's text through a spam checker on the server before posting
>> it...
> OK, if you are able to setup that on the master server, please do so ;)
> I'll then patch the user notes script to use it (just tell me what I
> need to run).
Spam checkers don't work (particularly well). Especi
> I hope that my reasons are understandable, and I am certain that we will
> be able to manage to execute some smooth process of handing the
> reposibilities and the credits over. It was a great pleasure to work
> with you, and shape the PHP Documentation into what it is today.
Well, Goba, let me
Sebastian-H. Picklum wrote:
> Ohhh. Since when do we have that? Seems that I missed the news... :-)
It's been around for quite a while. 1.5 years, I'd guess. I blogged
about it a few months back.
S
> Another option (in the short-term) is to simply required a valid email
> address (most of the spam seems to come from the default
> '[EMAIL PROTECTED]' or 'php-general@lists.php.net').
Haven't checked the code recently, but I'm pretty sure a blank name
results in php-general@lists.php.net and a
1 - 100 of 463 matches
Mail list logo
