On Wed, 17 Nov 2010 00:01:04 +0100, Mats wrote:
I suggest that you provide a patch, eg. changeset, with ChangeLog
all to possibly get some more attention. If you can, use patcher to
construct the mail. Send it to xemacs-patches. Mark is with [AC21.5].
I understand that it is nice to have people use your specialized tools
and workflows to submit patches.
But you are also creating a barrier to contribution with them.
I could probably have read about how to find/install/configure patcher,
figured out the preferred way to write ChangeLog messages for XEmacs,
that I should mark the email with [21.5], and send it to xemacs-patches
- if I thought I was ready to actually send patches that I would have
committed myself had I had a commit-bit.
But I am not at that stage in contributing yet - I am basically learning
to crawl before I walk. The two patches I sent was me trying to start a
discussion: "Is this the right way to fix this problem? Or maybe this
By including a patch in my question, I hoped to indicate that I actually
took the time to try a fix for the problem, and that I did try to
configure+compile with the change - that I wasn't just randomly making
I had hoped for one of two outcomes: Someone either says "Yeah, that's a
good fix", or says "No, it should be done in this way instead", and
either commits it with the appropriate extra bits and bobs, or says I
should submit the suggested, corrected solution through the proper channels.
As a green newcomer, I don't want to learn - and go through - all the
hoops to send a patch only to have someone say that it should have been
fixed in a slightly different way.
Maybe I am too lazy to contribute, I don't know :-)
"Right. Why waste time learning, Adam Sjøgren
when ignorance is instantaneous?" asjo(a)koldfront.dk
XEmacs-Beta mailing list