Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
A
asterisk
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
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Issue analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Voice
asterisk
Commits
0a06d397
Commit
0a06d397
authored
7 years ago
by
zuul
Committed by
Gerrit Code Review
7 years ago
Browse files
Options
Downloads
Plain Diff
Merge "CEL: Remove header declarations of non-existant functions."
parents
7898aad0
4e5cc70f
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
include/asterisk/cel.h
+0
-23
0 additions, 23 deletions
include/asterisk/cel.h
with
0 additions
and
23 deletions
include/asterisk/cel.h
+
0
−
23
View file @
0a06d397
...
...
@@ -87,29 +87,6 @@ enum ast_cel_event_type {
*/
unsigned
int
ast_cel_check_enabled
(
void
);
/*!
* \brief Allocate a CEL record
*
* \since 1.8
*
* \note The CEL record must be destroyed with ast_cel_destroy().
*
* \retval non-NULL an allocated ast_cel structure
* \retval NULL error
*/
struct
ast_cel
*
ast_cel_alloc
(
void
);
/*!
* \brief Destroy a CEL record.
*
* \param cel the record to destroy
*
* \since 1.8
*
* \return nothing.
*/
void
ast_cel_destroy
(
struct
ast_cel
*
cel
);
/*!
* \brief Get the name of a CEL event type
*
...
...
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