On Mon, 8 Feb 1999, Gilles Detillieux wrote:
> string. But, what do we do if it does? If we silently ignore the error,
> then the user won't find out right away that the database is corrupt.
> There's already a test & error message for bad tags, so I'd say do the
> same for a bad length or missing data. I may take a stab at it after my
> meeting this afternoon, but I can't promise.
I'm not convinced this can't wait. I'm starting to get too many "bug
reports" that are fixed in the current code. So let's leave tomorrow
afternoon as the "point of no return" and everyone has until then to fix
nits in the release. Unless I hear of a huge showstopper, I'll roll the
final release tomorrow night. I'll branch the CVS tree so we can still
release 3.1.1, 3.1.2, etc. if needed.
> If it's not too late, I'd like to slip in this little tweak to the new
> parse_date function in htnotify. It will recognize an ISO 8601 date
> yyyy-dd-mm instead. I hope to get a documentation patch to you before
> the end of the day as well, explaining date formats.
Sounds good.
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
