I did not get an email either (I do not use a gmail account) but would like to say have been a very satisfied user since the Windows Commander days.
I am currently using it with Windows 7 and because of the speed and ease of use, I recently was able to quickly and efficiently get my files off a dying machine for backup.
from: Total Commander mailing list <wincmd-list-delete AT ghisler DOT com>
reply-to: Total Commander mailing list <wincmd-list-delete AT ghisler DOT com>
to: utceditors AT gmail DOT com
date: Fri, Aug 3, 2012 at 9:55 PM
subject: Total Commander 8.01 released
mailed-by: ghisler.com
: Important mainly because of the people in the conversation.
The strange thing is that, the date is Aug 3, 2012, isn't supposed to be the date i actually received the mail Aug 3, 2013?
Isn't it obvious? Mr. Ghisler is experimenting with better undelete functionality using some kind of time travel/manipulating technology and it somehow leaked into his systems and sent the last year's anouncement again (at least it's how it appears to us in 2013). But we're lucky, imagine if it went some other way and for example made him 40 years younger (it's new and untested technology, who knows what it can do). Could be good for him (perhaps, in a way), but we would have to wait for new TC for quite some time, before he'd grow up again. :)
I was excited to see an announcement about a new version of Total Commander. Then I realized that nothing more can be added to this incredible program. That is when I realized there must be some kind of mistake.
Sorry, it was a misconfiguration of the server. I was using a Cron script to send the mailing at night. Unfortunately it's not possible to set the year in a Cron script, so the server re-sent the mailing exactly one year later. Sorry for the error!
Btw, the beta test for TC 8.5 will start soon. It's ready, but since a lot of people are on vacation now, it would probably not make much sense to start the beta test now...
ghisler(Author) wrote:Sorry, it was a misconfiguration of the server. I was using a Cron script to send the mailing at night. Unfortunately it's not possible to set the year in a Cron script, so the server re-sent the mailing exactly one year later. Sorry for the error!