On Mon, 24 May 2004, Gabor Hojtsy wrote:
> I think you misunderstood the point. We would not like to split up the
> stuff and host on different servers. We would better live with a server
> which is capable of serving our needs (building docs in HTML, PDF, etc.,
> regular building of revcheck info
On Mon, 24 May 2004, Gabor Hojtsy wrote:
> BTW Derick told me that the current docs. machine should not be made
> public. Maybe because of the bandwidth issues, I am not aware of the
> real reason...
It's not bandwidth issues, but just plain speed. If you want to use it
as a testbed fine, that's
We can get you a space for doc building and so forth, but right now
we're working on some other important stuff that takes precedence..
I would be happy if you would be able to find the time sometime, but so
far, there was always something else that took precendence. I *know* and
*understand* th
oc'; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [PHP-DOC] Re: distribution of INI information in the manual
I know you guys are overly prejudiced against systems@, but why not run it
on
our own systems??
--Wez.
SF does not allow you to host some website which is not
closely related
to t
04 15:19
To: Wez Furlong
Cc: 'Nuno Lopes'; 'Mehdi Achour'; 'PHPdoc'; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: [PHP-DOC] Re: distribution of INI information in the
manual
I know you guys are overly prejudiced against systems@, but
why not run it on
our own sy
Please turn of read-reciepts when posting to the mailing lists.
You can't possibly want to know when every single subscriber has read your
email.
> Hi all,
>
> I'm willing to host the livedocs site if everyone would like
> me to host it.
>
> Regards
> --jm
oc'; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [PHP-DOC] Re: distribution of INI information in the manual
I know you guys are overly prejudiced against systems@, but why not run it
on
our own systems??
--Wez.
> > SF does not allow you to host some website which is not
> cl
?).
--Wez.
-Original Message-
From: Gabor Hojtsy [mailto:[EMAIL PROTECTED]
Sent: 24 May 2004 15:19
To: Wez Furlong
Cc: 'Nuno Lopes'; 'Mehdi Achour'; 'PHPdoc';
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [PHP-DOC] Re: distribution of INI information in
004 15:19
> To: Wez Furlong
> Cc: 'Nuno Lopes'; 'Mehdi Achour'; 'PHPdoc';
> [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [PHP-DOC] Re: distribution of INI information in
> the manual
>
> > I know you guys are overly prejudiced
We have the server and all the hardware, but we need to wait for nexen
to set them up.
They have a lot of work, but I think that it will be on this summer.
(cc'ing gui from nexen and poz the donator)
didou
Wez Furlong wrote:
I know you guys are overly prejudiced against systems@, but why not run
I know you guys are overly prejudiced against systems@, but why not run it on
our own systems??
Our experience was that the guys at systems are already overloaded with
work, and it would probably not be a good idea to put more load on them.
There are some long awaiting stuff, which would need tha
I know you guys are overly prejudiced against systems@, but why not run it on
our own systems??
--Wez.
> > SF does not allow you to host some website which is not
> closely related
> > to the project you run on SF. We are not going to move the CVS to
> > SF.net, so it is not justifyable to put a
Now you made me curious on how old are you. :)
almost 18 :)
So you are going out of High Shool, not into it, right?
From the manual:
"A Literal is some specific piece of data, taken literally, from a computer
system. It is similar in some ways to UserInput and ComputerOutput, but is
somewhat more o
> Now you made me curious on how old are you. :)
almost 18 :)
> >>>- additional entities for a better consistency (&php; for
> >>> PHP for example, which will fix [1]
> >>
> >>Why is PHP a literal? It could be a or something but why a
> >>literal? BTW I am not entirely sure that an entitiy is ne
Sine only the ini_set() page is updated from time to time, this is
quite some duplicated stuff, and will no doubt confuse people. What
would be ideal IMHO:
- move extension relevant stuff to the extension pages
(do not have this info on the ini_set() page at all)
- move general INI settings ex
> >> Sine only the ini_set() page is updated from time to time, this is
> >> quite some duplicated stuff, and will no doubt confuse people. What
> >> would be ideal IMHO:
> >>
> >> - move extension relevant stuff to the extension pages
> >> (do not have this info on the ini_set() page at all)
Sine only the ini_set() page is updated from time to time, this is
quite some duplicated stuff, and will no doubt confuse people. What
would be ideal IMHO:
- move extension relevant stuff to the extension pages
(do not have this info on the ini_set() page at all)
- move general INI setti
Gabor Hojtsy wrote:
Cheers,
Aloa
[snip]
Sine only the ini_set() page is updated from time to time, this is quite
some duplicated stuff, and will no doubt confuse people. What would be
ideal IMHO:
- move extension relevant stuff to the extension pages
(do not have this info on the ini_set(
18 matches
Mail list logo
