for SD
History
- 2009-01-27 00:46:11 jesse 910 local
-
due keeps getting set from blank to blank and recorded as a txn (257)
- 2009-01-27 00:01:38 jesse 909 local
-
owner should autocomplete with the list of all the existing ticket owners (254)
- milestone changed from cavil to diana
- 2009-01-26 22:33:05 jesse 908 local
-
Comment on: mirroring from a replica with no new changesets seems to take a while (283)
- created set to 2009-01-26 22:33:05
- original_replica set to 09E374FA-EBD3-11DD-9A7A-BF638F31E82D
- creator set to jesse
- content set to I've dealt with the case where we don't record merge tickets if we haven't seen something new from the remote replica. What we need to deal with next is recognizing when a remote replica is a clone of one we've seen before without reading all the remote changesets
- ticket set to E22CC20C-EB2F-11DD-86E4-E6238F31E82D
- 2009-01-26 22:33:05 jesse 907 local
-
mirroring from a replica with no new changesets seems to take a while (283)
- milestone changed from cavil to diana
- 2009-01-26 20:27:55 spang 905 269A0F94-E928-11DD-8654-E6598232C628
-
sd log needs docs (286)
- owner set to spang@bestpractical.com
- creator set to spang
- original_replica set to 269A0F94-E928-11DD-8654-E6598232C628
- status set to new
- reporter set to spang@bestpractical.com
- created set to 2009-01-26 20:27:55
- component set to core
- summary set to sd log needs docs
- milestone set to cavil
- 2009-01-26 20:27:32 spang 904 269A0F94-E928-11DD-8654-E6598232C628
-
prophet log options are confusing (275)
- status changed from open to closed
- 2009-01-26 20:27:20 spang 903 269A0F94-E928-11DD-8654-E6598232C628
-
Comment on: prophet log options are confusing (275)
- created set to 2009-01-26 20:27:20
- creator set to spang
- original_replica set to 269A0F94-E928-11DD-8654-E6598232C628
- content set to We now have <since>..<until>-style range-specifications, and --all to specify show it all. You can use LATEST~# to specify an offset from the latest changeset.
- ticket set to 4FF1E1D0-E73B-11DD-8B64-D4548232C628
- 2009-01-26 03:14:02 jesse 1130 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
-
mirroring from a replica with no new changesets seems to take a while (283)
- owner set to jesse@bestpractical.com
- 2009-01-25 22:38:42 jesse 902 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
-
the prompt in the cli has the cwd rather than project name (284)
- summary changed from the promt in the cli has the cwd rather than project name to the prompt in the cli has the cwd rather than project name
- status changed from new to closed
- 2009-01-25 22:32:53 jesse 901 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
-
the prompt in the cli has the cwd rather than project name (284)
- owner set to jesse@bestpractical.com
- creator set to jesse
- original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
- status set to new
- reporter set to jesse@bestpractical.com
- created set to 2009-01-25 22:32:53
- component set to cli
- summary set to the promt in the cli has the cwd rather than project name
- milestone set to cavil
- 2009-01-25 22:31:18 jesse 900 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
-
mirroring from a replica with no new changesets seems to take a while (283)
- created set to 2009-01-25 22:31:18
- summary set to mirroring from a replica with no new changesets seems to take a while
- component set to core
- creator set to jesse
- original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
- status set to new
- milestone set to cavil
- reporter set to jesse@bestpractical.com
- 2009-01-24 07:56:18 spang 897 269A0F94-E928-11DD-8654-E6598232C628
-
prophet log options are confusing (275)
- summary changed from what on earth does sd/prophet log actually do? to prophet log options are confusing
- 2009-01-24 07:51:54 spang 896 269A0F94-E928-11DD-8654-E6598232C628
-
sd settings needs test coverage (274)
- status changed from new to closed
- 2009-01-21 14:54:43 spang 892 AC4C038C-E6CF-11DD-B0EC-203D8232C628
-
sd ticket show shouldn't work on comments (281)
- owner set to spang@bestpractical.com
- 2009-01-21 14:41:43 spang 891 AC4C038C-E6CF-11DD-B0EC-203D8232C628
-
Comment on: sd ticket show shouldn't work on comments (281)
- created set to 2009-01-21 14:41:43
- creator set to spang
- original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
- content set to spang@loki:~> sd ticket show 134 = METADATA id: 134 (56CE1ABC-E7C9-11DD-8428-D7A28232C628) (134 is a comment)
- ticket set to 9EDE0A7E-E7C9-11DD-9477-1BA38232C628
- 2009-01-21 14:41:43 spang 890 AC4C038C-E6CF-11DD-B0EC-203D8232C628
-
sd ticket show shouldn't work on comments (281)
- created set to 2009-01-21 14:41:43
- summary set to sd ticket show shouldn't work on comments
- component set to core
- creator set to spang
- original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
- status set to new
- milestone set to cavil
- reporter set to spang@bestpractical.com
- 2009-01-21 14:40:48 spang 889 AC4C038C-E6CF-11DD-B0EC-203D8232C628
-
prophet log options are confusing (275)
- status changed from new to open
- 2009-01-21 14:39:42 spang 888 AC4C038C-E6CF-11DD-B0EC-203D8232C628
-
Comment on: prophet log options are confusing (275)
- created set to 2009-01-21 14:39:42
- creator set to spang
- original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
- content set to It gives a list of recent changes, afaict. But it's broken.
- ticket set to 4FF1E1D0-E73B-11DD-8B64-D4548232C628
- 2009-01-23 02:38:34 jesse 892 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
-
Comment on: "add a comment" and "initial comments" boxes should be centered (253)
- created set to 2009-01-23 02:38:34
- creator set to jesse
- original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
- content set to Done.
- ticket set to A73627C0-E5CA-11DD-830A-3DB1457005E2
- 2009-01-23 02:38:34 jesse 891 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
-
"add a comment" and "initial comments" boxes should be centered (253)
- status changed from new to closed