Issues holding up 1.6.0 release.

[Rob Browning]

Right now, I'm waiting on someone to tell me what I should do about
scm_call_with_dynamic_root.  I don't feel like that's a decision I
should make on my own, unless people indicate they want me to.  In
particular:

  - should we create the new function that doesn't (re/un)wind the
    dynamic-wind stack?

  - should this function go into 1.5.3, or should apps like guppi,
    scwm, and possibly gnucash just continue to copy-paste from root.c
    for the next release?

  - I think we already know what the function should look like, but
    what should the new function be named, and should it show up on
    the scm side, or just the C side?

In addition to this issue, I need to transplant my 64-bit fixes to the
stable and unstable trees.

What else?

Thanks

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD