>>> On 25.06.2013 08:46, Christian Stoller wrote:
What do you think about moving the PHP documentation to a Git repository,
mirrored on Github? Doing this would make it possible for everybody to
extend the documentation easily by creating pull requests.
What do you think?
Even
On 20 June 2013 14:36, Julien Pauli wrote:
> On Wed, May 15, 2013 at 3:54 PM, Julien Pauli wrote:
>>
>> Hi all,
>>
>> As you know, 5.5 final is coming soon.
>> We are in RC, so mainly stabilizing stuff and preparing the final release
>> for anyone to setup 5.5 on their servers.
>>
>> I see the do
On 16 June 2013 15:37, Sherif Ramadan wrote:
> I have no clue how you're getting that result.
What are your respective mbstring.func_overload settings, out of interest?
Adam
On 12 June 2013 13:18, Yannick Torrès wrote:
> The FR documentation actually didn't build.
> configure.php don't tell me where, nether with the --enable-xml-details :/
>
> Is there someone who can help us with this ?
Here's the first part of what I get (the important bit would seem to
be the clas
(Cross-posted from the bugspam list.)
On 25 May 2013 12:10, wrote:
> This behaviour is common across almost all functions, and we have a
> note to that effect on the "Internal (built-in) functions" page
> (http://php.net/manual/en/functions.internal.php):
>
> Note: If the parameters given to
On 26 May 2013 02:06, Manmohan Bishnoi wrote:
> Just wanted to know that whether this is a BUG or the documentation
> structure has been under major changes ?
This is a bug — specifically, https://bugs.php.net/bug.php?id=64842, I
believe. I don't think anyone who knows about CHM generation has ha
On 21 January 2013 09:08, Ferenc Kovacs wrote:
> http://about.travis-ci.org/docs/user/notifications/
> we don't have a custom notifications set up, so the default behavior will be
> used when sending out the email on broken builds.
Is the owner of the repository in this case phpdoc@lists.php.net?
On 21 January 2013 08:48, Hannes Magnusson wrote:
> I assume that much, but... and what?
> Do we get a mail on build failure? Does it notify the author who broke
> the build?
> Whats the purpose?
I can't answer how it's set up now, but one advantage down the track
would be the integration with Gi
On 10 January 2013 02:05, Levi Morrison wrote:
> Firstly, I apologize if this is the incorrect list.
It's more phpdoc and php-notes, so I've cc:d those lists in. Thanks
for pitching in!
Here's some background reading from a user note discussion last year:
http://marc.info/?l=phpdoc&m=13463994551
On 29 December 2012 07:04, Levi Morrison wrote:
> 1. The documentation pages need to be full-page width. They are
> far too narrow in their current state. They also need more gutter
> room.
Weirdly, I think they're more readable in their current state than
full width. I seem to be outnumbered
On 21 December 2012 07:29, Philip Olson wrote:
> appears moderately sane
You don't have to be crazy to work here, but it helps.
Welcome aboard!
Adam
On 20 December 2012 16:06, wrote:
> The en build of the PHP Manual is broken, so it does not validate or build.
> Please fix it! ;)
Fixed. Insert the usual reminder about the benefits of checking your
commits through configure.php before committing them. :)
> Love,
> The docs.php.net s
On 31 August 2012 21:56, Daniel Brown wrote:
> On Fri, Aug 31, 2012 at 6:16 AM, Hannes Magnusson
> wrote:
>>
>> It isn't scaling, but we do have crapload of people with php.net
>> karma, and all of them have the ability to edit/reject notes.. Most
>> simply don't know it.
>> I think we should try
tl;dr: I am become death, the destroyer of user notes. (I hope.)
Hi everyone,
As many of you know, user notes have been a long-standing hobby horse
for me. About six weeks ago, I decided to do something useful about
them, and subscribed to the mailing list to try to help moderate the
stream of in
On 6 August 2012 15:05, wrote:
> The en build of the PHP Manual is broken, so it does not validate or build.
> Please fix it! ;)
I've reverted r326993 for now, which caused the breakage.
Herman, did you forget to svn add the GearmanException documentation?
Thanks,
Adam
On 24 July 2012 15:04, wrote:
> The en build of the PHP Manual is broken, so it does not validate or build.
> Please fix it! ;)
Fixed. Appropriate person whacked with newspaper.
> Love,
> The docs.php.net server
Kisses,
Adam
On 4 May 2012 04:05, wrote:
> Your documentation is broken. The build is done on Friday.
Fixed. Usual admonishments about checking that your XML is valid
before committing apply. :)
Adam
On 22 February 2012 10:50, Philip Olson wrote:
> If we want to join the GSoC then I'm guessing we'll need to lead the charge.
> Please speak up if you're willing to administrate the GSoC for the entire
> PHP project.
I did put my hand up for that on IRC a week or two back, so I'm still
fine with
On 21 February 2012 05:00, wrote:
> Your documentation is broken. The build is done on Friday.
Fixed. Insert usual grumble about people not running configure.php here. :)
Adam
On 16 February 2012 05:00, wrote:
> Your documentation is broken. The build is done on Friday.
>
> Please, try to fix it *quickly*.
Just under four hours. I'm going to call that quick. Build fixed.
Adam
On 21 July 2011 12:07, Hannes Magnusson wrote:
> On Thu, Jul 21, 2011 at 20:14, Adam Harvey wrote:
>> On 21 July 2011 07:15, Hannes Magnusson wrote:
>>> A (short) list of "authors" or a "group" needs to exist due to licensing
>>> issues.
>>&
On 21 July 2011 07:15, Hannes Magnusson wrote:
> A (short) list of "authors" or a "group" needs to exist due to licensing
> issues.
> How to generate that one I've no idea.
Are you sure about that? I think you'll find that copyright is held by
all contributors individually, so it's actually more
On 27 April 2011 11:10, Daniel Convissor
wrote:
> On Fri, Apr 22, 2011 at 10:08:20AM +0200, Hannes Magnusson wrote:
>> There was at some point discussion about merging the
>> http://phpsec.org/ doc into the manual, but I think that went nowhere
>> as those peeps didn't want to play ball.
>
> As on
On 28 January 2011 10:53, Daniel Convissor
wrote:
> A quick reminder that one thing that seemed to be agreed upon during the
> last discussion is that mentions of older versions in the text (like
> "available since") should be moved to the change log on the given page.
I think that's a good gener
On 15 January 2011 23:46, Daniel Brown wrote:
> On Sat, Jan 15, 2011 at 05:52, Julien Pauli wrote:
>>
>> Last time (http://marc.info/?l=phpdoc&m=128686832705180&w=2) , we
>> suggested that [old-and-not-supported-versions] = PHP4 + PHP5.0 +
>> PHP5.1 ; and [up-to-date-versions] = PHP5.2 + PHP5.3
>
On 10 January 2011 17:02, Karoly Negyesi wrote:
> This http://paste.pocoo.org/show/318170/ would be more correct but it
> contains a non ASCII Unicode character. May I commit it still?
Documentation files are explicitly UTF-8 (per the XML header), so as
long as the ℤ is encoded in UTF-8, it shoul
On 6 January 2011 14:15, Apache wrote:
> The build of the PHP Manual is broken, so it does not validate or build.
> Please fix it! ;)
Fixed in r307153.
> Love,
> The docs.php.net server
Hugs and kisses,
Adam
On 8 November 2010 19:00, Richard Quadling wrote:
> [1] vs [2]
>
> Not asking for a change or anything.
I think it's probably OK the way it is: the manual page is
specifically for MongoId, and the capitalisation's quite distinct from
any other meaning there. The URL might be a touch unfortunate,
On 3 October 2010 08:43, Robinson Tryon wrote:
> Is there
> any chance that the code examples in the manual are also available
> under a different license as well?
As you've seen on the licensing page, the manual — including the code
examples — is only available under the CC-BY licence. Given the
Hi Ambrish,
On 16 September 2010 16:58, Ambrish Bhargava1 wrote:
> With the release of v1.9.0 of IBM_DB2 extension, one documentation change is
> required for db2_pconnect() API.
>
> Attached patch file contains the changes. The change log corresponding to
> this documentation can be seen at: h
On 2 June 2010 01:21, Alex Cartwright wrote:
> As a use case: Harry visits the FAQ to see what the value of 'K' means, it
> shows that K means 1 Kibibyte. As Harry knows what a Kibibyte is, he knows
> that 'K' should be 1024 bytes. Adam on the other hand, has no idea what a
> Kibibyte is and so co
On 2 May 2010 20:56, Partha Sarathy wrote:
> Could you please tell / suggest me how to develop Plagiarism Checker feature
> or send some useful articles / free APIs and so on.
Please note that this mailing list is intended for discussing the
development of the PHP documentation, and is not a gene
On 31 March 2010 22:25, Christopher Jones wrote:
> It's not clear if/how these features are going to be re-included.
>
> I'd prefer to see them commented out. Displaying mis-information is
> harmful to the overall PHP project.
Agreed. We can always reincorporate documentation for any features
th
33 matches
Mail list logo
