Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
TLMSP curl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CYBER - Cyber Security
TS 103 523 MSP
TLMSP
TLMSP curl
Commits
49c0d62d
Commit
49c0d62d
authored
23 years ago
by
Daniel Stenberg
Browse files
Options
Downloads
Patches
Plain Diff
two items since pre6
parent
f752098b
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CHANGES
+12
-0
12 additions, 0 deletions
CHANGES
with
12 additions
and
0 deletions
CHANGES
+
12
−
0
View file @
49c0d62d
...
...
@@ -7,6 +7,18 @@
History of Changes
Daniel (6 March 2002)
- Ralph Mitchell patched away a few compiler warnings in tests/server/sws.c
Daniel (5 March 2002)
- I noticed that the typedef in curl.h for the progress callback prototype was
wrong and thus applications that used it would not get the proper input
data. It used size_t where the implementation actually uses doubles!
I wish I could blame someone else, but this was my fault. Again.
Version 7.9.5-pre6
Daniel (4 March 2002)
- Cut off the changes done during 2001 from this changelog file and put them
in a separate file (CHANGES.2001), available from CVS of course.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment