Closed (fixed)
Project:
modr8
Version:
6.x-1.0-beta2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Jul 2008 at 14:53 UTC
Updated:
23 Sep 2008 at 10:42 UTC
Jump to comment: Most recent file
Comments
Comment #1
pwolanin commentedcan you please re-post the patch without a # in the name? I cannot open the link because of that.
Comment #2
eMPee584 commentedwow that's true sorry.. *g
Comment #3
niklp commentedIs this going anywhere? Is it in dev? HEAD?
Comment #4
pwolanin commentedcommitted - thanks
Comment #5
eMPee584 commentedcool thx pwolanin... btw would you mind to also make 6.x-dev releases on each CVS commit? don't know how much work it is but it helps stay on track, f.e. my little update script uses the date of dev tarballs to slurp newest ones off the server..
Comment #6
niklp commentedAgain, there are still no clues as to "where this is fixed" - can someone PLEASE add this information? Lots of people are trying their hardest to use 6.x stuff. Modules are all over the place, still, and lack of this kind of information is just confusing as hell.
Many thanks.
Comment #7
eMPee584 commentedNikLP don't quite now if i understood you correctly, but if you meant that literally, pwolanin has committed this to CVS HEAD, which is the only place to get it because this module does not yet have a dev release. It's only a silent warning anyways so please calm down ;)
Comment #8
pwolanin commentedeMPee584 - if you want to stay current like that, I'd suggest deploying via CVS.
I'll push a 1.0 with this fix anyhow.
Comment #9
eMPee584 commentednah CVS has them stupid hidden folders ;)
but almost all packages i have installed do -dev-releases so except for a few my method works nicely.
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.