Skip to content
GitLab
Menu
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
Per Cederqvist
lyskom-server-ceder-1616-generations-topgit
Commits
03cd78a7
Commit
03cd78a7
authored
Nov 02, 1995
by
Per Cederqvist
Browse files
Added preliminary news for 1.8.0.
parent
1c8f487f
Changes
1
Hide whitespace changes
Inline
Side-by-side
NEWS
View file @
03cd78a7
NOT
RELEASED
YET
Changes
in
lyskomd
1.8.0
(
Release
date
1995
-
11
-??)
--------------------------------------------------
*
WARNING
:
This
release
of
lyskomd
contains
an
incompatible
change
in
the
database
format
.
Once
lyskomd
1.8.0
saves
the
database
you
cannot
revert
to
older
versions
of
1.7.1
.
This
is
because
a
Conf
-
type
now
is
8
bits
long
.
The
protocol
is
,
of
course
,
backwards
compatible
,
so
you
do
not
need
to
upgrade
the
clients
to
be
able
to
run
lyskomd
1.8.0
.
Just
make
sure
you
save
a
copy
of
your
database
.
*
If
configured
with
--
with
-
gnu
-
malloc
lyskomd
will
use
the
GNU
malloc
package
instead
of
the
system
-
supplied
malloc
.
GNU
malloc
is
included
in
the
distribution
.
*
The
asynchronous
message
async_rejected_connection
is
now
sent
at
most
once
per
minute
.
*
Lyskomd
1.8.0
implements
protocol
A
level
8.
See
doc
/
prot
-
A
.
txt
for
information
about
the
new
features
it
contains
.
*
You
can
now
specify
where
lyskomd
should
dump
core
(
if
that
should
ever
happen
)
using
the
"Core directory"
parameter
.
*
Can
now
handle
1500000
texts
and
4765
persons
/
conferences
.
*
Text
garbing
can
now
be
turned
off
completely
from
the
config
file
.
*
dbck
-
t
now
dumps
a
list
of
all
existing
text
numbers
to
stdout
.
*
Some
minor
portability
fixes
.
Some
bug
fixes
.
See
the
various
ChangeLogs
for
details
.
Changes
in
lyskomd
1.7.1
(
Release
date
1995
-
01
-
08
)
--------------------------------------------------
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment