checkwatches --all should be --reset
Bug #442993 reported by
Graham Binns
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
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.
| Changed in malone: | |
| milestone: | 3.1.10 → 3.1.11 |
Revision history for this message
| Graham Binns (gmb) wrote Re: [Bug 442993] Re: checkwatches --all should be --reset | #1 |
| Changed in malone: | |
| milestone: | 3.1.11 → 3.1.10 |
| assignee: | nobody → Graham Binns (gmb) |
| status: | Triaged → Fix Committed |
| Changed in malone: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This has already landed; there's no need to re-target it, is there?