Hi,
Here is the TSRM diff file in unified diff format.
I have used the command: cvs diff -uN
Regards,
Ananth.
>>> Marcus Boerger <[EMAIL PROTECTED]> 1/30/2004 12:31:43 PM >>>
Hello Ananth,
please provide a unified diff (cvs di -u) and we cannot accept
precompiler statements starting after colu
On Thu, 29 Jan 2004, Ananth Kesari wrote:
> Oops. I did not know that the system only accepts text/plain
> attachments. Here is the attachment for TSRM diff. This is in
> text format. I will send the diff for the whole project soon.
In unified diff pretty please? :) (cvs diff -u)
regards,
Derick
Hello Ananth,
please provide a unified diff (cvs di -u) and we cannot accept
precompiler statements starting after column 0. You *must* keep
this in mind. For a full list of rules to follow you can visit
the file CODING_STANDARDS.
regards
marcus
Friday, January 30, 2004, 7:11:23 AM, you wrote:
Oops. I did not know that the system only accepts text/plain
attachments. Here is the attachment for TSRM diff. This is in
text format. I will send the diff for the whole project soon.
Thanks,
Ananth.
>>> Derick Rethans <[EMAIL PROTECTED]> 1/29/2004 5:26:01 PM >>>
On Thu, 29 Jan 2004, Ananth Kesa
On Thu, 29 Jan 2004, Ananth Kesari wrote:
>could be to begin working on some simple defects and fix them.
>Can you let me know if I can do that and if yes, how? I mean,
>where to look for the defects filed and what is the procedure to
>start fixing them?
Here are some (longish) urls that list
On Thu, 29 Jan 2004, Ananth Kesari wrote:
> Our changes are spread across many files, so I am not sure if we can
> checkin at this stage of the release of PHP 5.0. Anyway, I have
> attached the diff file for TSRM. Please review the same and give me
> your comments. There are similar changes in oth
Hi,
Our changes are spread across many files, so I am not sure if we can
checkin at this stage of the release of PHP 5.0. Anyway, I have
attached
the diff file for TSRM. Please review the same and give me your
comments.
There are similar changes in other files. If you think I should send
across
th
Hi,
We are indeed in a feature freeze. However, if your diff is simple and well
written, we could consider including it (basically as a bug fix for novell).
Please send a diff so that we can see if it's something which can go in. It
really depends on the extent of your patch.
If we feel it's too
Ananth Kesari wrote:
Hi Derick,
How do you want me to do this? Should I check in a couple of files
with NetWare modifications into CVS which you will take a look at
or should I send the modified file over mail to this group for review
before checking in?
what about mailing the "cvs diff" results?
Hi Derick,
How do you want me to do this? Should I check in a couple of files
with NetWare modifications into CVS which you will take a look at
or should I send the modified file over mail to this group for review
before checking in?
Thanks,
Ananth.
>>> Derick Rethans <[EMAIL PROTECTED]> 1/21/20
Hi Andi,
Now that it is in code-freeze stage, when is PHP 5.0 going to be
released?
We have NetWare changes of approximately about 200 to 250 lines
(maybe even more) spread across many files that include, TSRM, ZEND,
sapi modules, extensions, ext/standard, main and netware directories.
Thanks,
An
On Wed, 21 Jan 2004, Ananth Kesari wrote:
> I am working on porting PHP 5.0 onto NetWare. I would like to start
> checking in the changes into the PHP 5.0 source code branch. What is the
> project name that I need to check in?
Please show us some patches first. I remember from last time that a lo
At 04:48 AM 1/21/2004 -0700, Ananth Kesari wrote:
Hi,
I am working on porting PHP 5.0 onto NetWare. I would like to start
checking in the changes into the PHP 5.0 source code branch. What is the
project name that I need to check in?
Ananth,
We are in a code-freeze now. You are welcome to commit b
13 matches
Mail list logo
