Am Freitag, 7. April 2006 06:36 schrieb David Hampton:
> On Thu, 2006-04-06 at 22:59 +0200, Christian Stimming wrote:
> > The latest 1.9.x releases *used* to write a data file that could still be
> > read by 1.8.12. That was a very convenient way to get used to the new
> > version but all the while
On Fri, 2006-04-07 at 11:17 +0200, Christian Stimming wrote:
> Does that mean 1.9.4 shipped with this problem? If yes, then for anyone
> who needs to fix this manually: The workaround is to open the 1.9.4
> datafile with a text editor (potentially running "gunzip -c
> compressedfile > cleartextfil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Hampton schrieb:
> On Thu, 2006-04-06 at 22:59 +0200, Christian Stimming wrote:
>> The latest 1.9.x releases *used* to write a data file that could still be
>> read
>> by 1.8.12. ...
>> However, with one of the "commodity namespace" related cha
On Thu, 2006-04-06 at 22:59 +0200, Christian Stimming wrote:
> The latest 1.9.x releases *used* to write a data file that could still be
> read
> by 1.8.12. That was a very convenient way to get used to the new version but
> all the while keep the 1.8.12 version around and working. My data file
On Thu, 2006-04-06 at 22:59 +0200, Christian Stimming wrote:
> The latest 1.9.x releases *used* to write a data file that could still be
> read
> by 1.8.12. That was a very convenient way to get used to the new version but
> all the while keep the 1.8.12 version around and working. My data file
The latest 1.9.x releases *used* to write a data file that could still be read
by 1.8.12. That was a very convenient way to get used to the new version but
all the while keep the 1.8.12 version around and working. My data file in
question is quite simple -- no business features, no stocks, but n
