aMule Forum
English => en_Bugs => Topic started by: Morse on August 22, 2008, 05:15:29 PM
-
bandwidth control to be precise.
bandwidth limits adjusting doesn't change the real limits in the core - only in amulegui. it can be easily seen by relaunching amulegui - limits are the same.
adjusting in "preferences -> connection" works fine.
-
Thanks for the report, will be investigated and fixed.
-
2.2.3 - still here
i'm using linux amuled from packman's repository and amulegui SVN 29.12.08 from ftp://kieselei.de/aMule-Win32/ (since there is no other choices). may be there is some EC conflict?
-
No, it was just... khmm... forgotten.
-
I've finally installed 2.2.4, so i can say - it's still here!
i think this bug would be GonoszTopi's personal nightmare ;D
-
And I can tell you that it will be there in the next release. I just don't feel like fixing it :P (Actually I don't feel like anything, although I should have done that "next release" at least a week ago -- being too busy and ill: an unfortunate coincidence).
-
Sorry to hear that, hope you are getting better soon.
Fixed in 9592 (trunk). Backport ?
-
If it doesn't break anything, backport.
Gonosz, do you want me to take over this release?
-
Thx, I'll do it tomorrow.
Repeat, next release: 7th Apr
-
I'd like to have this (http://www.amule.org/amule/index.php?topic=16664.msg89880#msg89880) cleared up first.
Hell, I don't even feel like joking about 7th Apr being in 2010.
-
Isn't it soon(TM) enough?
Btw, a little more delay doesn't mean any difference. (I'll increase the version number every day, so we may find ourselves releasing 2.2.337 next...)
-
2.2.337?...
Since even the current version has a name "we didn't have a .4 version since... well... long ago", you have to think of a real funny name for such a release number, as i can't even imagine for how long you didn't have a .337 ;D