Re: [PHP-DEV] (change request) PHP 4.0 Bug Summary Report
On Sun, 06 May 2001, Jani Taskinen wrote: I thought about having those urls too..but as you said, it'll get too big to be send on the list. But what if the summary with URLs could be requested for? From some webpage maybe? Or via email? At some point Rasmus used to have a page that listed all open bugs with a link to edit each bug. I don't remember where it was, exactly. -Andrei The church is near but the road is icy; the bar is far away but I will walk carefully. -- Russian proverb -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] (change request) PHP 4.0 Bug Summary Report
On Sun, 06 May 2001, Jani Taskinen wrote: I thought about having those urls too..but as you said, it'll get too big to be send on the list. But what if the summary with URLs could be requested for? From some webpage maybe? Or via email? At some point Rasmus used to have a page that listed all open bugs with a link to edit each bug. I don't remember where it was, exactly. bugs.php.net/lbugs.php Stands for lite-bugs originally done for Andy because he wanted a lower-bandwith way to list them all. -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] (change request) PHP 4.0 Bug Summary Report
Thanks Rasmus. This lbugs.php is just enough. No need to emails. :) --Jani On Mon, 7 May 2001 [EMAIL PROTECTED] wrote: On Sun, 06 May 2001, Jani Taskinen wrote: I thought about having those urls too..but as you said, it'll get too big to be send on the list. But what if the summary with URLs could be requested for? From some webpage maybe? Or via email? At some point Rasmus used to have a page that listed all open bugs with a link to edit each bug. I don't remember where it was, exactly. bugs.php.net/lbugs.php Stands for lite-bugs originally done for Andy because he wanted a lower-bandwith way to list them all. -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] (change request) PHP 4.0 Bug Summary Report
At 02:02 PM 5/5/01 -0400, Joe Brown wrote: Is it possible to include www.php.net/bugs.php?id= at the front of these, or on a second line trailing each bug listed? Would make the list twice as long, but a lot simpler to follow up on, w/mail reader that recognises links. The bug summary is already large enough, we've had to increase the maximum allowed message size on php-dev just to accomodate it. -Andrei -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] (change request) PHP 4.0 Bug Summary Report
Hi Joe!
On Sat, 05 May 2001, Joe Brown wrote:
Is it possible to include www.php.net/bugs.php?id= at the front of these, or
on a second line trailing each bug listed?
Would make the list twice as long, but a lot simpler to follow up on, w/mail
reader that recognises links.
[justa-hint]
make yourself a script which replaces the bug id with that.
or define a mapping for a reformating key to do it (in ~.vimrc)
map ^[[24~ :/==/,$!awk '{gsub(/^[0-9]+/,http://www.php.net/bugs.php?id=;
$1,$1);print $0} ' -^M
so if you edit the message with vim and hit f12 you get what you want.
-- teodor
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] (change request) PHP 4.0 Bug Summary Report
On Sat, 5 May 2001, Andrei Zmievski wrote: At 02:02 PM 5/5/01 -0400, Joe Brown wrote: Is it possible to include www.php.net/bugs.php?id= at the front of these, or on a second line trailing each bug listed? Would make the list twice as long, but a lot simpler to follow up on, w/mail reader that recognises links. The bug summary is already large enough, we've had to increase the maximum allowed message size on php-dev just to accomodate it. I thought about having those urls too..but as you said, it'll get too big to be send on the list. But what if the summary with URLs could be requested for? From some webpage maybe? Or via email? --Jani -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
