mailinglists:

Hi!

...

...

Well - one thing I'd like to change: Instead of swapping I'd like to put the current master on top of the stack; I had wanted this for a while too; you got me to do something about it.

:-)) Thanks alot - still didn't find time to learn some haskell :-(

...

promote :: X ()

Just did a fast check - but it seems to do what I meant - THANKS alot!

...

I would send a darcs patch, but I don’t know where it should go. A new module seems overkill, the name DwmPromote doesn’t apply to it, and renaming DwmPromote.hs to Promote.hs would break peoples’ setups.

Hm. I put this in my local config - by I think this is something that should be in XMonadContrib. I don't know about the xmonad development policy about backwards compatibility, but it sounds more 'clean' to me just to rename DwmPromote to Promote and add a new 'cyclePromote' or 'pushPromote' (wheee, finding a good name is sometimes not easy :-(().

What is the 'normal' process in such a case? Make it clean and break configs? Or better add another module?

If there's an argument that some people might use the old behaviour, better to have a new module. We can then deprecate it, and remove it in the next release. -- Don