Re: [PHP-DEV] Re: Developer Seeking To Help
One common way is to create your patches and post them either to the php-dev list or as a comment (prefered) in the bug db, and if they are useful, the dev team will have a good reason to give you cvs access. (Use unified diff format for patches.) I have recently updated the FTP extension to include a couple of more functions (send raw command and get the raw response body), and I would like to send the patch now. Is all I need to know available in man patch? -- Best regards, Ivan Ristic, Chief Technology Officer DataGate Network Solutions Ltd. - http://www.datagate.net Tel: +44 8700 119090, Fax: +44 8700 119080 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: Developer Seeking To Help
On Mon, 4 Feb 2002, Ivan Ristic wrote: I have recently updated the FTP extension to include a couple of more functions (send raw command and get the raw response body), and I would like to send the patch now. Is all I need to know available in man patch? diff -u oldfile.c newfile.c (or if you worked on a CVS check out of the tree): cvs diff -u filename.c regards, Derick -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Developer Seeking To Help
Hello, Chris Shiflett wrote: I know there are also mundane tasks that need accomplishing, and I would be more than willing to help with some of these as well. Suggestion: have a go at the bug database, talk to the QA team and see what is most urgent to be fixed. That would be of a great help. Regards, Manuel Lemos -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: Developer Seeking To Help
On Sun, 3 Feb 2002, Manuel Lemos wrote: Manuel, Thank you for the suggestion. If you would be so kind, I have a few questions. 1) How can I change the status of a bug? For example, I was looking through session bugs (since that's most likely where I could contribute the easiest) and read a bug #14227. This bug is bogus and is the result of the submitter not understanding HTTP and the Set-Cookie header enough. I would love to be able to act as a mediater of sorts, so that the bogus bugs can be filtered to save developers some time. I can even give elaborate explanations in the beginning to make sure people know why it's bogus. :) 2) If a bug is legitimate, and I know how to fix it, how do I go about doing this? Must I receive permission for a CVS account? How does one gain the trust to be able to commit changes? 3) How do I know if someone is working on a bug? If it is open status, can I safely assume it's not been investigated by a member of the PHP development team? Thanks for the information. Chris Hello, Chris Shiflett wrote: I know there are also mundane tasks that need accomplishing, and I would be more than willing to help with some of these as well. Suggestion: have a go at the bug database, talk to the QA team and see what is most urgent to be fixed. That would be of a great help. Regards, Manuel Lemos -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: Developer Seeking To Help
On Sun, 2002-02-03 at 16:29, Chris Shiflett wrote: On Sun, 3 Feb 2002, Manuel Lemos wrote: Manuel, Thank you for the suggestion. If you would be so kind, I have a few questions. 1) How can I change the status of a bug? For example, I was looking through session bugs (since that's most likely where I could contribute the easiest) and read a bug #14227. This bug is bogus and is the result of the submitter not understanding HTTP and the Set-Cookie header enough. I would love to be able to act as a mediater of sorts, so that the bogus bugs can be filtered to save developers some time. I can even give elaborate explanations in the beginning to make sure people know why it's bogus. :) You need to either be a developer (i.e. have a cvs account) or be the original bug poster to modify a bug's status. As a developer, this is done from the 'Developer' tab in the bug db interface. 2) If a bug is legitimate, and I know how to fix it, how do I go about doing this? Must I receive permission for a CVS account? How does one gain the trust to be able to commit changes? One common way is to create your patches and post them either to the php-dev list or as a comment (prefered) in the bug db, and if they are useful, the dev team will have a good reason to give you cvs access. (Use unified diff format for patches.) Alternatively, you could just ask for a cvs account and hope you get one--if your patches suck, it will eventually be revoked, I guess. :) 3) How do I know if someone is working on a bug? If it is open status, can I safely assume it's not been investigated by a member of the PHP development team? If someone is *really* into working on a bug themselves, it will be 'Assigned' in the bug db to that person's account id. If the bug's status is not 'Assigned' (sometimes 'Analyzed' is used here too) then you should be able to safely engage the bug in combat. Thanks for the information. Chris Hope it helps, Torben -- Torben Wilson [EMAIL PROTECTED] http://www.thebuttlesschaps.com http://www.hybrid17.com http://www.inflatableeye.com +1.604.709.0506 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
