don't generate HTML tables with more than 50 lines, as browsers generally
can't cope with huge tables.

option to skip the database check (since that code doesn't work with
all versions of MySQL/Msql-mysql/Perl/moonphase).

different fields we keep an activity log on.  The bugs_activity table
now has a pointer into that table instead of recording the name directly.

Set up a new, highly experimental email-notification scheme.  To turn
it on, the maintainer has to turn on the "New email tech" param, and
then individual users have to turn on the "New email tech" preference.

Don't try to put out the footer if we're shutdown (as that can try to access the DB which we don't want).

table.  There is now a separate entry for each new long description,
rather than appending them all together in one big field.

both was causing corruption on about 1 in 40 passwords.)

to be consistant with the way it gets listed in bug lists.

is this much faster, but it also lets you sort by that column, and
requires less special-case code.

of all the keywords assigned to the bug.  Right now, we only have code
that generates and maintains this field; soon will come code that
actually uses it.

reassigning by component, reassign the qa contact too.

choose from in the footer.

me.  Added a footer to every page.  Add some options to do things like
display checkboxes instead of scrolling lists, and a new formatting
for email diffs, and show list items capitalized instead of all upper
case.

away from them or they get removed from the CC list.

changing keywords.