History

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

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

prophet log options are confusing (275)

• status changed from new to open

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

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

"add a comment" and "initial comments" boxes should be centered (253)

• status changed from new to closed

Comment on: prophet log options are confusing (275)

• created set to 2009-01-22 04:58:26
• creator set to jesse
• original_replica set to 4AA041B6-E5C6-11DD-A0BF-4BB0457005E2
• content set to It should work similarly to git log/svn log. it shows you transaction history for your database
• ticket set to 4FF1E1D0-E73B-11DD-8B64-D4548232C628

prophet log options are confusing (275)

when you try to clone a replica and it fails, the target is still created (277)

• owner set to spang@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-21 22:24:35
• component set to core
• summary set to when you try to clone a replica and it fails, the target is still created
• milestone set to cavil

Comment on: prophet log options are confusing (275)

• created set to 2009-01-20 21:43:02
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• content set to Whatever it does, it appears to be broken.
• ticket set to 4FF1E1D0-E73B-11DD-8B64-D4548232C628

prophet log options are confusing (275)

• owner set to spang@bestpractical.com
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• status set to new
• reporter set to spang@bestpractical.com
• created set to 2009-01-20 21:43:02
• component set to core
• summary set to what on earth does sd/prophet log actually do?
• milestone set to cavil

no help exists for sd settings (230)

• status changed from new to closed

sd settings needs test coverage (274)

• owner set to spang@bestpractical.com
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• status set to new
• reporter set to spang@bestpractical.com
• created set to 2009-01-20 21:09:15
• component set to core
• summary set to sd settings needs test coverage
• milestone set to cavil

sd clone http://fsck.com/~jesse/sd-bugs should work (264)

• status changed from new to closed

flow for templates with errors is bad (232)

• status changed from open to closed

prop values should be able to be force-set with ! (249)

• status changed from open to closed

Comment on: give is broken (272)

• created set to 2009-01-20 20:33:15
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• content set to As far as I can tell, give is intended to be invoked like: sd ticket give id email But this doesn't work, because of interactions between its syntax and more general rules in the prophet/sd dispatchers. Should look into.
• ticket set to 9084E2A6-E731-11DD-9F4B-BD458232C628

give is broken (272)

• owner set to spang@bestpractical.com
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• status set to new
• reporter set to spang@bestpractical.com
• created set to 2009-01-20 20:33:15
• component set to core
• summary set to give is broken
• milestone set to cavil

non-interactive ticket update should not update props that didn't change (268)

• status changed from new to closed

Comment on: props with recommended values are not fully extensible (270)

• created set to 2009-01-20 09:43:48
• creator set to spang
• original_replica set to AC4C038C-E6CF-11DD-B0EC-203D8232C628
• content set to Say, if I'm running a project and want to add an extra prop with a list of valid values along the lines of status. Well, I can't without editing SD, because that new prop would have to have a _recommended_values_for_prop_$prop method.
• ticket set to D6561D96-E6D6-11DD-9BD9-FE428232C628