checkwatches --all should be --reset

Bug #442993 reported by Graham Binns on 2009-10-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Medium
Graham Binns

Bug Description

Fixing bug 439258 added an option, --all, to checkwatches.py. However, this is a bit disingenuous, because it doesn't hint at the fact that cancelling a checkwatches run when --all has been specified will leave all the bug watches on a bug tracker un-updated and with a lastchecked value of None, meaning that checkwatches will check them the next time it runs.

To make it a bit more explict, --all should be renamed to --reset.

Deryck Hodge (deryck) on 2009-10-20
Changed in malone:
milestone: 3.1.10 → 3.1.11

This has already landed; there's no need to re-target it, is there?

Deryck Hodge (deryck) on 2009-10-20
Changed in malone:
milestone: 3.1.11 → 3.1.10
assignee: nobody → Graham Binns (gmb)
status: Triaged → Fix Committed
Graham Binns (gmb) on 2009-11-09
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers