Re: Implement -exec-jump

[Eli Zaretskii <eliz@gnu.org>]

> Date: Wed, 8 Apr 2009 14:57:44 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, Andr? P?nitz <andre.poenitz@nokia.com>, 	gdb-patches@sources.redhat.com
> 
> > Another way to do it would be to add pending items to a GDB release wiki
> > page. Joel already uses this, in fact. So it's the easiest to implement.
> 
> This mechanism is fine as far as I am concerned.

I'd agree to that as a fallback, but I'd prefer to codify the current
unwritten practice that code patches come with docs patches.

The reason is that deferring documentation to when a release is
impending would almost certainly mean that documentation in general
and my free time in particular will be a roadblock on the way to a
release.  Also, some of the contributors might not be available then,
which means we will have a dilemma: either release undocumented
features or try to document them by someone who knows much less than
the original author of the code.

We had no problems until now with requesting docs (and a test case)
together with the code.  Why should we deviate from that now?