Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
all
-
None
Description
This request originated from a mailing list request to provide a new parm on the commit command to allow a bug ID to be specified and stored as a rev prop. ghudson then added the following suggestion: "On the other hand, I've long felt that it would be a good idea to be able to set arbitrary rev-props in a commit. If we had a good syntax for that, it would be almost as convenient as your proposed -id flag." Here is the mailing list thread (the discussion spawned from another discussion so the subject does not match). The thread contains some UI suggestions. http://www.contactor.se/~dast/svn/archive-2004-07/1197.shtml Perhaps this should be a second issue dependent on this issue, but I would also like to have a way to require these properties to be specified, just as --message is required. An idea would be to supply a name=regex pair in the configuration area that could be used to validate and require the property to be set. It is definitely a secondary requirement but in the case of something like a bug ID, it would be useful to be able to mandate that one be specified.
http://www.contactor.se/~dast/svn/archive-2004-07/1197.shtml