Enrico Forestieri wrote: > So it is broken and will stay broken? It is not that important, after > all this simply avoids an empty "TeX Information", but I am really > annoyed that seemingly everything which is cygwin related is not > well accepted.
Bullshit. In my case I don't have the energy nor time to actively backport this. If you want things to go in 1.4, then - send patches against 1.4 (step by step, one fix = one patch) - explain why it is needed - explain how well it is tested - explain potential risks (or the lack thereof) - ask for inclusion - commit it (yourself) if OK I am sure that you will get more positive feedback if you follow this procedure. Obviously nobody has enough time, therefore everybody does what he cares about most. For example, I wanted configure.py in 1.4 because that means less work for me when doing configure related changes. Therefore I did the backport work. Other example: I will look at the bigl UI because I could use this feature. I don't think that LyX on cygwin should be broken, but I don't use it, so I am less motivated to spend time on cygwin stuff. Georg
