This message was submitted incomplete to the accidently pressing enter on this keyboard. Here is the email as it was inteded to go out.
-- Email Hi Everyone, Someone recommended that I started working on something that I feel bothers me or I need. Well, one of thing I miss is the commit templating capability that cvs has. This feature allows the repository manager or project leader to establish the basic structure of the commit message that they wish to use for their project. This helps obvioudly review the log information so that it is not just a long list of changes. Instead it provides additional useful information, and it would provide a way to create templates that would allow for easy parsing, for integrating with other systems. Example: PR Number: Submitted By: Reviewed By: Approved By: Description: MTN: ---------------------------------------------------------------------- MTN: Please fill out this commit message. MTN: MTN: Enter a description of this change. MTN: Lines beginning with `MTN:' are removed automatically. MTN: MTN: Current branch: head MTN: Changes against parent 7d72b4f63082eab237b029d0ff1980f0be374f7a MTN: patched main.cpp MTN: ---------------------------------------------------------------------- 1) What does everyone think of this idea? 2) Should a template file be stored in _MTN maybe call template? 3) Should the template be stored in the DB, so that all developers that work on a specific project gets the wanted template when performing a commit? Regards, Pablo
_______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
