[Mono-winforms-list] New to the list

[Jonathan Pobst]

Awesome, we love people who fix the bugs they find!

Generally a bug is opened in bugzilla and the patch is attached to it. 
This makes sure they don't get ignored on the list and are trackable. 
But if they're pretty minor, I can probably take them from the list and 
make sure they get committed.

Ideally, each .patch file will contain all the files for one 'bug'. 
That allows us to commit and test each change independently.

So maybe "bug one" patch file has changes to:
Form.cs
ChangeLog

and "bug two" patch file has changes to:
Control.cs
ThemeWin32Classic.cs
ChangeLog

Go ahead and patch the ChangeLog with your message saying what was 
changed and why (what it fixes) following the format of other messages.

If possible (and things like cosmetic changes aren't), it's also nice to 
provide NUnit tests that ensure the issue is fixed and never creeps back in.

Thanks for your help in tracking these down and providing fixes!
Jonathan


Ernesto wrote:
> Hi,
> 
> I'm new to the list (and to Mono).
> 
> I'm trying to run a rather large Win Forms MDI application with Mono 
> 1.2.5 and found some minor bugs that made Mono crash when running this app.
> 
> I have some (really minor) bugfixes and cosmetic changes to some 
> controls and I was wondering if I should send them directly to the list.
> Should I just attach a .patch or .diff file to a post?
> Should I send a patch for multiple files or one individual patch for 
> every file?
> Should I send the change log as part of the post body or as a patch to 
> the ChageLog file?
> 
> Thanks in advance.
> 
> Regards,
> Ernesto
> 
> _______________________________________________
> Mono-winforms-list maillist  -  Mono-winforms-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-winforms-list
> 
>