Re: All get_class()-bugreports out ... but how about these?

From: Date: Thu, 26 Feb 2004 15:50:15 +0000
Subject: Re: All get_class()-bugreports out ... but how about these?
References: 1  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-749@lists.php.net to get a copy of this message
Oh, hmm - didn't notice that. Well, maybe then we should rename the directory directly on the server to LiveUser if this is okay for the devs? I guess Martin or somebody could do that without loosing CVS history. I'll include Lukas in CC of this mail. We already talked about the problems with the HEAD-branch. However it already was a "mass-check" on all packages which took quite a while. I'm not sure how you would like to solve this problem. Klaus, do you volunteer to check every package if it has a different branch besides HEAD? Would be quite helpful, surely. By the way: I not only checked packages in CVS but also the latest packages available with download-all using prefered_state devel ... Stefan On 26 Feb 2004 at 16:42, Klaus Guenther wrote: > Perm_LiveUser is very much alive as LiveUser :-) > > I'm unsure of the status of the others. > > But something else -- you only were able to check HEAD, but when a > package has branches, it might be that you only checked a branch that > is no longer being developed, while the actively developed branch may > be the one with the problems. > > Just something to think about... > > ----- Original Message ----- > From: "Stefan Neufeind" <stefan@neufeind.net> > To: "pear-qa" <pear-qa@lists.php.net> > Sent: Thursday, February 26, 2004 4:33 PM > Subject: [PEAR-QA] All get_class()-bugreports out ... but how about > these? > > > > Hi PEARs, > > > > as you might have noticed all get_class()-bugreports are out now. > > But during the searches I came across these packages in CVS which > > don't seem to exit anymore or maybe not yet / never existed. > > > > How about them? Does anybody know about a status of these? Which > > could maybe be cleaned from the CVS server?

« previous php.pear.qa (#749) next »