X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-SourceIP: 95.97.163.245 X-Authenticated-Sender: b DOT mykendevelopment AT upcmail DOT nl Message-ID: <55B8AF94.1050405@iae.nl> Date: Wed, 29 Jul 2015 12:48:52 +0200 From: myken User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] What is the current version of PCB References: <55B7AEFD DOT 9060307 AT iae DOT nl> <201507281639 DOT t6SGdKZn002381 AT envy DOT delorie DOT com> In-Reply-To: <201507281639.t6SGdKZn002381@envy.delorie.com> Content-Type: multipart/alternative; boundary="------------050705060501050808040104" Reply-To: geda-user AT delorie DOT com 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 
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--