Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
lyskom-server-ceder-1616-generations-topgit
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Per Cederqvist
lyskom-server-ceder-1616-generations-topgit
Commits
033d7e05
Commit
033d7e05
authored
Aug 28, 1998
by
Per Cederqvist
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Added more tests and documentation.
parent
f07c4369
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
0 deletions
+15
-0
ChangeLog
ChangeLog
+15
-0
No files found.
ChangeLog
View file @
033d7e05
1998-08-28 Per Cederqvist <ceder@gratia>
Added more tests and documentation.
* src/server/testsuite/lyskomd.0/01.exp: Added tests for requests
51-62.
* doc/Protocol-A.texi (LysKOM Data Types): The order of the
elements in Who-Innfo-Old was wrong. The same bug existed at
least as far back as in the prot-A.txt file that was distributed
with the 1.7.0 server. I find it better to change the
documentation than the code.
(create-person-old): Document the auto-login feature.
(who-is-on): Clarify which sessions that are returned.
(get-unread-confs): Clarify that this request may return extra
conferences. This request may not be made before you log in.
1998-08-27 Per Cederqvist <ceder@gratia>
Added more tests and documentation.
...
...
Write
Preview
Markdown
is supported
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