Hello Shyamal.
It looks to me like Stephen made a response to the patch, indicating some
further changes he'd like to have seen. Could you make those changes and
submit a patch? Once we're happy with it, it will definitely go in, and
likewise for any further, similarly-vetted code you send. The vetting
process may seem like somewhat of a hassle right now, but if you follow
through, I imagine the process will get smaller and smaller as you come to
learn how to follow the conventions.
(In the meantime, you might consider writing up what you've learned. We
have a section on coding conventions, currently sitting in the newest
versions of the XEmacs Internals Manual but soon to move to the general-docs
package. That section mostly covers writing C code, but you could extend
that with a section on writing documentation.)
Ben> In the meantime, take a look at the latest GNU docs.
Much of
Ben> the stuff there can be lifted straight into XEmacs.
I have looked at the GNU docs. However, Stephen had warned me
not to copy from there without "express permission":
http://list-archive.xemacs.org/xemacs-beta/200409/msg00310.html
Not knowing the significance of this I simply wrote each and
every line in the patch without looking into the GNU manual
very much at all during the period. I believe the patch is up
to the latest GNU docs, but different in detail (e.g. Emacs
does not ship old-c-mode, and CC mode is built in, XEmacs
uses a package system, etc.)
I wrote to RMS about this. He said that he would probably grant approval
for stuff taken from the GNU manual, provided we showed him stuff first. We
need test cases, so by all means go ahead and use stuff from the GNU manual,
and you will be of great service.