Nice :)<br><br>However, does the same apply to themes? See <a href="http://drupal.org/node/137062">http://drupal.org/node/137062</a><br><br>&quot;...for sites that deploy Drupal
directly from CVS, it helps if you commit this change to the .info file
for your theme. This is also a good way to indicate to users of each
theme what version of core the <a href="http://drupal.org/handbook/cvs/introduction#HEAD">HEAD</a> of CVS is compatibile with at any given time.&quot;<br><br><div><span class="gmail_quote">On 6/19/07, <b class="gmail_sendername">
Derek Wright</b> &lt;<a href="mailto:drupal@dwwright.net">drupal@dwwright.net</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>On Jun 14, 2007, at 11:53 PM, Dries Buytaert wrote:<br><br>&gt; That&#39;s probably a good idea.<br><br>Done.&nbsp;&nbsp;See <a href="http://drupal.org/node/152819">http://drupal.org/node/152819</a> if you happen to care.<br><br>
All &quot;version&quot; definitions from all .info files on all branches of the<br>contrib repo are now gone.<br><br>All relevant handbook docs have been updated to tell people not to do<br>this.<br><br>In the future, if you check out from CVS and see &quot;version&quot; defined,
<br>please file an issue with the maintainer and scold them. ;)<br><br>Thanks,<br>-Derek (dww)<br><br><br></blockquote></div><br><br clear="all"><br>-- <br>Regards,<br>&nbsp;&nbsp;Johan Forngren :: <a href="http://johan.forngren.com/">
http://johan.forngren.com/</a>