<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 7/01/2011 7:13 AM, Rossen Apostolov wrote:
<blockquote cite="mid:4D262261.5040504@kth.se" type="cite">Hi again,
<br>
<br>
A few quick notes on using redmine. Have a look at the wiki at
<a class="moz-txt-link-freetext" href="http://www.redmine.org/projects/redmine/wiki/Guide">http://www.redmine.org/projects/redmine/wiki/Guide</a> provides
information about the general usage.
<br>
</blockquote>
<br>
Excellent.<br>
<br>
One feature that I think we should be using is the ability of
Redmine to cross-reference repository commits with issue tracking.
<a class="moz-txt-link-freetext" href="http://www.redmine.org/projects/redmine/wiki/RedmineSettings#Referencing-issues-in-commit-messages">http://www.redmine.org/projects/redmine/wiki/RedmineSettings#Referencing-issues-in-commit-messages</a>
observes that a commit message of "<code>This commit refs #1, #2 and
fixes #3</code>" will create the appropriate URL cross-references
in those three issues. Conversely, in Redmine discussion, the use of
"commit:c6f4d0fd" displays a link to that commit with text
"c6f4d0fd". This should enhance the usability of Redmine as a
discussion forum, because you can get access to source code contents
and git diffs in the browser at the click of a link.<br>
<br>
I think it would be overkill to require the creation or linking of a
Redmine issue for every commit, however. Thoughts?<br>
<br>
Mark<br>
<br>
</body>
</html>