<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 06/24/2010 09:21 PM, Christopher Samuel wrote:
<blockquote
cite="mid:D45958078CD65C429557B4C5F492B6A6088CD6B9@IS-EX-BEV3.unimelb.edu.au"
type="cite">
<meta http-equiv="Content-Type"
content="text/html; charset=ISO-8859-1">
<meta name="Generator"
content="MS Exchange Server version 6.5.7654.12">
<title>SVN commit messages</title>
<!-- Converted from text/plain format -->
<p><font size="2">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Hi folks,<br>
<br>
I've just seen a couple of SVN commit messages go past<br>
when I sync'd my local git clone of Torque which didn't<br>
mean that much to me, they were:<br>
<br>
SVN 3761 "RT8044 fixed"<br>
SVN 3760 "updates to code"<br>
SVN 3748 "Fixed the description"<br>
<br>
It'd be nice if a bit more context could be given, for<br>
example "Fixed broken test for job dependencies (RT8044)",<br>
"Updates to regular expressions and removal of unneeded<br>
Perl code in tests" or "Fixed copy and paste error in the<br>
description of the qdel test".<br>
<br>
I'm not having a go at the developers in question, I<br>
really appreciate what they do, just that it would make<br>
it easier for us outside to track what's going on with<br>
the code.<br>
<br>
cheers!<br>
Chris<br>
- --<br>
Christopher Samuel - Senior Systems Administrator<br>
VLSCI - Victorian Life Sciences Computational Initiative<br>
Email: <a class="moz-txt-link-abbreviated" href="mailto:samuel@unimelb.edu.au">samuel@unimelb.edu.au</a> Phone: +61 (0)3 903 55545<br>
<a moz-do-not-send="true"
href="http://www.vlsci.unimelb.edu.au/">http://www.vlsci.unimelb.edu.au/</a><br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.10 (GNU/Linux)<br>
Comment: Using GnuPG with Mozilla - <a moz-do-not-send="true"
href="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</a><br>
</font><br>
</p>
</blockquote>
Chris,<br>
<br>
Thank you for your comment. I will tell our engineers here to be more
descriptive and to qualify their references to internal ticket numbers.
I will try to be less curt on my entries as well.<br>
<br>
Ken<br>
</body>
</html>