Alexander Kellett wrote:
i see this frequently with many projects
can ruby-doc house a maintained repo for
such modifications to make sure they get in
to the relevant repo's?
What's a repo?
there's nothing worse than seeing work
slide into a void because people are too
busy in my opinion.
Yes, the question is what's the best way to avoid duplication.
The doc changes need to get merged into the current Ruby source. If the
lib owner does not respond to inquires, the a post to ruby-core may be
in order (unless there is someone here who can review & verify the
changes and do the commit.)
If changes are made to the core code, I can then grab the current 1.8
source and rebuild the docs*. Changes made to the standard lib should
be reflected in the uploads managed by Gavin Sinclair.
James Britt
* Clearly a job for ruby + cron
| 
