patch submitted by st.n@gmx.net (Stephan Niemz [faniz])

Remember This Query should give option to add to page footer
patch submitted by st.n@gmx.net (Stephan Niemz)

cleaning up trailing whitespace in buglist.cgi source. (no code changes)  Patch by Stephan Niemz [faniz] <st.n@gmx.net>

Fix for bug 66058: dates in Created and Changed date columns in buglists are now in context with how old the bug is.

within the last 18 hours: time only (12:24:34)
within the last   6 days: weekday and time (Fri 12:24)
within the last 100 days: month and day (01-19)
older than 100 days: previous behaviour (2001-01-19)

patch by dave@intrec.com (Dave Miller)

patch by the ever present dave@intrec.com

patch submitted by dave@intrec.com (Dave Miller), legend added
by cyeh@bluemartini.com

patches by zach@zachlipton.com. Thanks!

omission in the original patch.

submitted by mhamby@logicon.com (Mark Hamby).

change '@::legal_resolution_no_dup' to '@::settable_resolutions'. This a list of  resolutions which a bug may be changed to in the bug form and consists of all legal resolutions except 'MOVED' and 'DUPLICATE', since setting a bug to those resolutions requires a special process.

Bug moving code is now fully implemented. To use it, turn on the param and set the move related params.

Keywords were already enforced to never differ only in capitalization.  So, changed the code so that case no longer matters when typing in the name of a keyword.

than one table that have a field with that name.

change it to order by the sortkey of the target_milestone first.

of different target milestones by product.

seems useful and appropriate.)

string wasn't working with modern MySQL engines.

have a universal (and more noticable) way of displaying them.

to the shadow database.

bug queries can be run against it, so that these slow queries won't be
able to tie up the rest of the system.

of places.

"editbugs" and "canconfirm".  People without these states are now much
more limited in what they can do.

For backwards compatability, by default all users will have the
editbugs and canconfirm bits on them.  Installing this changes as is
should only have one major visible effect -- an UNCONFIRMED state
will appear in the query page.  But no bugs will become in that state,
until you tweak some of the new voting-related parameters you'll find
when editing products.

"check all" and "uncheck all" buttons work on IE.

is uglier, but often squeezes things better horizontally.