I can't make any promises. It's obvious from how little I've done since the last several times I said I planned to do something, that I am not doing very much. Anyway, there is never any reason someone else shouldn't work on it if they want to.
As for merging changes upstream, post to oskit-users about that. I can't speak directly for the Utah folks, but they are friends and have no interests contrary to ours. There has been very little oskit development there for a long time now. If there starts to be a high pace of work outside and no time on the Utah side to keep up, then I think they will be amenable to blessing a new public home for oskit development. Anyway, I think the only barrier now to changes getting merged and new releases getting made is manpower. If there is a clean and well-tested patch, they will be amenable to putting it in when someone has time to do the physical commits and the release legwork. I still have access and expect permission to make known-good changes in the Utah repository, and can perform release legwork in a pinch. _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
