in
c623734632010e4601ca4e369851bc79ab7f706f because it overrode an
existing method by the same name (awful.client.cycle).
The online documentation can't be fixed without making a release,
right? So maybe someone could cherry-pick
c623734632010e4601ca4e369851bc79ab7f706f to 3.4.x -- whatever the next
release branch
On Tue, Sep 25, 2012 at 1:15 PM, Uli Schlachter psyc...@znc.in wrote:
On 17.09.2012 16:00, Anurag Priyam wrote:
The online documentation can't be fixed without making a release,
right? So maybe someone could cherry-pick
c623734632010e4601ca4e369851bc79ab7f706f to 3.4.x -- whatever the next
c623734632010e4601ca4e369851bc79ab7f706f to 3.4.x -- whatever the next
release branch is supposed to be, so we don't miss out on it in the
next release?
Meh. That would break user configs with a micro release for no good reason.
Yes,
it is bad that this function is called differently between 3.4 and master
by the same name (awful.client.cycle).
The online documentation can't be fixed without making a release,
right? So maybe someone could cherry-pick
c623734632010e4601ca4e369851bc79ab7f706f to 3.4.x -- whatever the next
release branch is supposed to be, so we don't miss out on it in the
next release
