Mail Archives: geda-user/2015/07/29/06:46:40
This is a multi-part message in MIME format.
--------------050705060501050808040104
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
>> To my knowledge PCB uses the yyyymmdd format as the version numbering,
>> how does that relate to version 2.0?
> That file is ancient. Probably dates back to when we (Harry) thought
> there would be a 2.0 ;-)
>
Shouldn't someone do a git rm on that file? Or rather do a *git rm -r
README_FILES* on the directory because all information in it is ancient.
While we are at it, we could also remove the file README.cvs_branches
because the information is no longer up-to-date.
I don't have git access, so I can't do it.
Files with old information might confuse new developers, well it
confused me at least.
Cheers, Robert.
--------------050705060501050808040104
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<blockquote cite="mid:201507281639 DOT t6SGdKZn002381 AT envy DOT delorie DOT com"
type="cite">
<blockquote type="cite">
<pre wrap="">To my knowledge PCB uses the yyyymmdd format as the version numbering,
how does that relate to version 2.0?
</pre>
</blockquote>
<pre wrap="">
That file is ancient. Probably dates back to when we (Harry) thought
there would be a 2.0 ;-)
</pre>
</blockquote>
Shouldn't someone do a git rm on that file? Or rather do a <b>git
rm -r README_FILES</b> on the directory because all information in
it is ancient.<br>
While we are at it, we could also remove the file
README.cvs_branches because the information is no longer up-to-date.<br>
I don't have git access, so I can't do it.<br>
<br>
Files with old information might confuse new developers, well it
confused me at least.<br>
<br>
Cheers, Robert.<br>
<br>
</body>
</html>
--------------050705060501050808040104--
- Raw text -