"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
>>>>> "Hrvoje" == Hrvoje Niksic
<hniksic(a)srce.hr> writes:
Hrvoje> You don't follow xemacs-patches, do you? :-)
Hmm. As someone who hasn't been following xemacs-patches, I wonder:
Suppose you don't read the patches, only the ChangeLogs and the
explanation (if any). Do you think that's enough to understand what
the bugs and improvements are, and their importance?
It's not. The ChangeLog is only a guide that tells you what part of
the code changed, and the reason, but it is almost never sufficient to
understand the extent of the change. You have to look at the patch
for that.
For example:
Hrvoje> I fixed that bug last week. It's been annoying me for
Hrvoje> ages. If you're curious, I can tell you where the bug
Hrvoje> was.
If this is an easily introduced bug, maybe it would be instructive
to explain it here, and maybe prevent someone else from falling into
the trap.
It's a bug. Nothing more, nothing less. Not an intrinsic problem
with elisp, or anything like that.
OTOH, if that would be obvious if one reads xemacs-patches
I try to accompany each patch with a rationale why the patch is needed
and a description what the patch does. This does not apply to all the
patches, though. If I had done that for my "isearch FSF merge" patch,
I would have written a novel.
But yes, I think a careful reader of xemacs-patches should find it
very instructive.
Of course once I judge the patch important, I should read the patch
itself. What I'm asking is "Do most patch submissions explain their
importance in 25 words or less?"
I think it takes more than twenty-five words. But less than a
hundred. :-)