Hi Mantis gents,

Just a heads up that resolution states like "unable to reproduce" become
difficult to parse (because of the upredictable whitespace) if one
wanted to implement automatic status resolution in integration of SCM
with issue-tracking (like Scmbug does). Perhaps "unable_to_reproduce"
would be acceptable ?

e.g. parsing something like:

status 547: resolved unable to reproduce
status 548: resolved duplicate 547
status 547: assigned kristis
status 547: reopened

is bound to cause problems. Solvable problems, but still usability
problems. Users could be trained to instead write:

status 547: resolved unable_to_reproduce

and Scmbug could be replacing all "_"s with " "s, but some users will
forget, and will have their commit messages refused, and will have to
try again.

Thanks,
Kristis

_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to