|--==> "GIN" == Golubev I N <gin(a)mo.msk.ru> writes:
GIN> According to its `ChangeLog', `debug' elisp package have not had
GIN> major changes of functionality for too long. In particular, it is
GIN> overdue for emacs sync. AFAIK, the most notable drawback of its
GIN> current state is lack of `gud-gdb-complete-command' implementing
GIN> gdb-style command line completion.
GIN> Is there a single todo list for things like this?
Only in the dark recesses of my mind. :-)
GIN> Is there currently any policy of porting emacs features into
GIN> `debug' package?
No. Just be careful and thorough.
GIN> If someone wants to tackle it, what procedure should he follow?
I would take this approach:
- Install the upstream version in your workspace. Test, test,
test, and test some more.
- XEmacserise any Emacs things that don't work with XEmacs
(doing it in such a way that it doesn't break Emacs
compatibility). Test, test, test.
- Go through our ChangeLog and if there is anything that the
sync wiped out that is still needed, add that. Test, test,
test.
- diff -u upstream_version your_version > E_patch.diff
Send that to the upstream maintainers.
- diff -u our_version your_version > XE_patch.diff
Send that to xemacs-patches(a)xemacs.org
- Seeing as though you have done such a fantastic job with the
sync, consider volunteering for the role of XEmacs Package
Maintainer of the debug package. :-) (contact me about
this).
Don't forget to do ChangeLog entries. And it would be great if you
could give me an occasional progress report just to keep me in the
loop.
Thanks ever so much for taking this on.
Have fun, and good luck with it.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|