Re: Error on PEAR web

From: Date: Tue, 02 Aug 2005 19:19:45 +0000
Subject: Re: Error on PEAR web
References: 1 2 3 4 5 6 7 8 9 10  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-39140@lists.php.net to get a copy of this message
Yes, you're right. Looking at the code, that may very well be the case. At any rate, there is an exception made for RFCs in the pepr code. I don't have time to get more into it, though. Looks like it could be easy to fix (look around lines 226-238). http://cvs.php.net/co.php/pearweb/public_html/pepr/pepr-proposal-edit.php?r=1.43#226 Klaus On 8/2/2005 9:12 PM, Jesper Veggerby Hansen spake the following words: > Wasn't there a thread a while ago, (sorry can't find it) concerning > something like this on a RFC, that mentioned chaning to proposal > required a PEAR .tgz file and therefore you couldn't change the RFC to > proposal (even though a RFC PEAR .tgz makes no sense). So they changed > it so that a RFC did not need to have a .tgz, file but others still > did? Or does my memory server me wrong. > > /Jesper > > Joe Stump wrote: > >>> >>> Anyway it's better to ask too much that do not ask at all :) >>> >>> btw, this problem is fixed. >> >> >> >> Any chance of fixing the PEPr bug I reported while you're in there? >> I still can't change my Draft to a Proposal. Or, if it's not a bug, >> can you (or someone else) tell me how it isn't a bug and how to >> change my Draft to a Proposal? Because clicking on the "Change >> status to Proposal" doesn't work for me. >> >> --Joe >> >> >>> >>> --Pierre >>> >>> -- >>> PEAR Development Mailing List (http://pear.php.net/) >>> To unsubscribe, visit: http://www.php.net/unsub.php >>> >>> >> >

« previous php.pear.dev (#39140) next »