Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
P
protobuf-c
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Libraries
protobuf-c
Commits
1dc2c8dd
Commit
1dc2c8dd
authored
Jun 02, 2014
by
Robert Edmonds
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
ChangeLog: --enable-code-coverage
parent
54881f48
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
0 deletions
+4
-0
ChangeLog
ChangeLog
+4
-0
No files found.
ChangeLog
View file @
1dc2c8dd
...
@@ -108,6 +108,10 @@ protobuf-c (1.0.0) UNRELEASED
...
@@ -108,6 +108,10 @@ protobuf-c (1.0.0) UNRELEASED
compiled against a protobuf-c header file from the exact same protobuf-c
compiled against a protobuf-c header file from the exact same protobuf-c
release.
release.
* Add a --enable-code-coverage option to configure, which enables a
"make check-code-coverage" build target. This generates a code coverage
report and requires the lcov tool to be installed.
* Update copyright and license statements throughout. The original
* Update copyright and license statements throughout. The original
protobuf code released by Google was relicensed from Apache-2.0 to
protobuf code released by Google was relicensed from Apache-2.0 to
BSD-3-Clause. Dave Benson also converted his license from BSD-3-Clause
BSD-3-Clause. Dave Benson also converted his license from BSD-3-Clause
...
...
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