{header_to} option can now be either a string or an array ref

{header_to} hash parameter can now either be a string containing a
valid RFC 822 email address or an array ref containing a list of RFC
822 email addresses

Conflicts:

	lib/Log/Fine/Handle/Email.pm
Add blib and pm_to_blib to list of ignored items

Add blib and pm_to_blib to list of ignored items so they don't show up
in vc-dir

Conflicts:

	.gitignore
Clean up msgWrite() logic

Clean up msgWrite() logic as inspired by Log::Fine::Handle::Email
Set object's {_err_str} when _fatal() is called

Set object's {_err_str} when _fatal() is called.  Useful for when
{no_croak} is set.
Recommend Try::Tiny v0.11

Recommend Try::Tiny v0.11
Use the mailx(1) command for grabbing headers under solaris

Use the mailx(1) command for grabbing headers under solaris as the
stock mail(1) command does not support the '-H' option.  Tested under
OpenSolaris.

NOTE: A cursory check of IBM AIX[1] shows that their implementation of
mail /does/ support the '-H' option, so no need to check for it
there.  The mileage on other SysV-ish systems may vary.

Footnotes:
[1]  Not to say that Log::Fine officially supports IBM AIX.  The
author does not have access to an AIX box with a recent version of
perl on it.

Conflicts:

	t/16-handle-email-smtp.t
	t/20-handle-email-mimelite-delivery.t
Brainstorm ideas for v0.61

Brainstorm ideas for v0.61

Conflicts:

	TODO
Remove older closed TODO items

Remove older closed TODO items

Conflicts:

	TODO
Update TODO list for LOGFINE-0-61

 - Prioritize where appropriate
 - Elaborate on existing TODO items
 - Add new _error() class TODO

Conflicts:

	TODO
Remove requirement for Test::Output

Remove requirement for Test::Output and do not pass {no_croak} during
construction.  Note that we do not need to redirect STDERR.

Conflicts:

	t/02-handle.t
Add new method _error()

Add a new method, _error(), that is inheritable from other objects and
change the default behavior of _fatal().  The new behavior is as
follows:

 - Calls to _error() will, by default, call _fatal() unless the
   {no_croak} attribute is set.  Should this be the case, then
   _error() calls cluck[1] instead.
 - _fatal() no longer honors {no_croak}

While here:

 - Update unit tests accordingly
 - Convert calls from _fatal() to _error() as appropriate
 - Call _error() in Handle::File-based objects in the event that we
   cannot write to a file handle.

Footnotes:
[1]  See Carp(3pm)

Conflicts:

	lib/Log/Fine.pm
	lib/Log/Fine/Handle/Email/EmailSender.pm
registerHandle() can now accept array refs

registerHandle() can now accept array refs containing valid
Log::Fine::Handle objects in addition to just a Log::Fine::Handle
object.  While here, update unit tests accordingly.
Add additional sanity checks

 - Make sure we have valid blessed objects where applicable
 - Utils.pm: Simplify OpenLog()
 - Update unit tests accordingly

Documentation will need to be cleaned up to reflect new behavior where
applicable

Conflicts:

	lib/Log/Fine/Handle/Email.pm
Close out TODO items

Close out the following TODO items:

 - registerHandle() modifications
 - Catch situation where we can't write to a file handle
 - Addition of _error() method
_error() if we are unable to close file handle

_error() should we be unable to close the file handle.  While here,
clean up commenting where applicable
Correct bug reporting email address

All bug reports should be emailed to bug-log-fine at rt.cpan.org

Conflicts:

	lib/Log/Fine/Handle/Email/EmailSender.pm
	lib/Log/Fine/Handle/Email/MIMELite.pm
Initial entry of Null Handle

Initial entry of Null Handle and associated unit tests.

Conflicts:

	MANIFEST
	t/boilerplate.t
Cancel enable/disable task

Cancel enable/disable task.  This really involves too much work and
API changes to implement.  Unless there's demand or I can find a good
justifiable use case, then I'm not going to bother.
Add and close null handle creation task

Add and close null handle creation task
Update misleading DESCRIPTION

The old description indicated that messages sent via this handle were
sent to /dev/null or NUL, which is misleading.  In reality, the module
completely ignores any messages given to it.