Activity log for bug #3927

Date Who What changed Old value New value Message
2005-11-05 18:29:12 Björn Tillenius bug added bug
2005-11-05 18:33:06 Björn Tillenius malone: status New Accepted
2005-11-05 18:33:06 Björn Tillenius malone: assignee bjornt
2007-05-21 21:31:19 Joey Stanford malone: statusexplanation
2009-09-08 07:01:58 Björn Tillenius malone: assignee Björn Tillenius (bjornt)
2011-05-30 08:06:57 William Grant removed subscriber Canonical Launchpad Engineering
2011-09-16 21:13:50 Curtis Hovey launchpad: importance Medium Low
2012-10-04 14:49:33 Curtis Hovey description It should'n be necessary to indent email commands, it just makes it harder to use. Initially it was thought that it was a good idea to be able to interleave commands with the comments, thus the indentation was used in order to indentify commands. It's often more naturally to write commands either in the beginning of the email, or in the end, so it's better to identify commands that way, instead of relying on indentation. This also makes it easier to strip commands from emails, so that they won't show up in the description and in the added comment. It should'n be necessary to indent email commands, it just makes it harder to use. Initially it was thought that it was a good idea to be able to interleave commands with the comments, thus the indentation was used in order to indentify commands. It's often more naturally to write commands either in the beginning of the email, or in the end, so it's better to identify commands that way, instead of relying on indentation. This also makes it easier to strip commands from emails, so that they won't show up in the description and in the added comment. Providing a leading symbol may make it easier to identify the start of command and allow commands to be anywhere in the email.
2012-10-04 23:44:41 Robert Collins summary No indentation of email commands email commands are tricky to use (due to requirement for indentation)