Activity log for bug #62250
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2006-09-25 06:06:36 | Martin Pool | bug | added bug | ||
| 2006-09-25 16:36:45 | John A Meinel | bzr: status | Unconfirmed | Confirmed | |
| 2006-09-25 16:36:45 | John A Meinel | bzr: importance | Untriaged | Wishlist | |
| 2006-09-25 16:36:45 | John A Meinel | bzr: statusexplanation | Our optional arguments are always required in order. It is probably standard practice to nest as mentioned. I'm concerned about entries which take lots of optional arguments, as it starts to get unclear at about 3: bzr foo [ONE [TWO [THREE]]] versus bzr foo [ONE] [TWO] [THREE] *however*, core probably doesn't have any commands that take more than 2 optional positional arguments, so we should be able to use standard notation. | ||
| 2017-11-09 00:40:20 | Jelmer Vernooij | tags | check-for-breezy | ||
| 2019-06-29 09:23:46 | Jelmer Vernooij | tags | check-for-breezy | ||
| 2019-06-29 09:23:51 | Jelmer Vernooij | bug task added | brz | ||
| 2019-06-29 09:23:55 | Jelmer Vernooij | brz: status | New | Triaged | |
| 2019-06-29 09:23:57 | Jelmer Vernooij | brz: importance | Undecided | Wishlist | |
| 2019-06-29 09:24:00 | Jelmer Vernooij | tags | bitesized help |
