WARNING: This server is unstable and will be retired in the next days. If you want to keep this forum available, please request immediately a migration on the Nabble Support forum. Forums that don't receive any migration request will be deleted forever.

 « Return to Thread: How to handle small ancillary bug fixes?

How to handle small ancillary bug fixes?

by Rory Plaire :: Rate this Message:

| View in Thread

I'm debugging an issue in `Castle.MicroKernel.Handlers.ParentHandlerWithChildResolver` and notice that `TryResolve` calls `parentHandler.Resolve` instead of `parentHandler.TryResolve`.
 
As I'm going to be submitting an issue with a proposed fix for `Castle.MicroKernel.Handlers.ParentHandlerWithChildResolver`, should I just put this in the same changeset, or are separate bug reports / tests preferred?
 
-r

--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@....
To unsubscribe from this group, send email to castle-project-devel+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.

 « Return to Thread: How to handle small ancillary bug fixes?