always create an issue else we forget.... too much stuff to do.
Then conversation is always good. Because we build a shared mindset and we all learn together
OK - done (2743) - I followed the instructions on
http://code.google.com/p/pharo/wiki/HowToContribute - which are great (by the way there are a few typos in that text, and here are simple corrections - i think its fairly easy to spot the sections they replace):
We value your fixes and we always try to look at them and give
feedback to you, this works best if you create a bug entry in
the bug tracker. Without it we may have problem giving you feedback
or letting you know that there is another fix.
The most important point is that you check your fix in a fresh
(probably latest) image. There are two alternatives to packaging your
code: You can send a changeset or a set of packages. For complex
changes that involves several packages use a slice as there is a much
better merging support. While we prefer packages, if it is
easier for you send changesets, then we accept those too.
Prepare a changeset with your changes. File it out. Important:
Put your Full name instead of your initials, as it will help up to contact
you which is often necessary. Only alphabetical
characters, and Do Not use any spaces.
Tim