Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up #included files in parser directory (#1465) #1467

Conversation

jrgemignani
Copy link
Contributor

Cleaned up #included files in the .c files in the parser directory. Additionally, fixed one that was at the backend root.

modified:   src/backend/age.c
modified:   src/backend/parser/cypher_analyze.c
modified:   src/backend/parser/cypher_clause.c
modified:   src/backend/parser/cypher_expr.c
modified:   src/backend/parser/cypher_gram.y
modified:   src/backend/parser/cypher_item.c
modified:   src/backend/parser/cypher_keywords.c
modified:   src/backend/parser/cypher_parse_node.c
modified:   src/backend/parser/cypher_parser.c

Cleaned up #included files in the .c files in the parser directory.
Additionally, fixed one that was at the backend root.

    modified:   src/backend/age.c
    modified:   src/backend/parser/cypher_analyze.c
    modified:   src/backend/parser/cypher_clause.c
    modified:   src/backend/parser/cypher_expr.c
    modified:   src/backend/parser/cypher_gram.y
    modified:   src/backend/parser/cypher_item.c
    modified:   src/backend/parser/cypher_keywords.c
    modified:   src/backend/parser/cypher_parse_node.c
    modified:   src/backend/parser/cypher_parser.c
@MuhammadTahaNaveed
Copy link
Member

@jrgemignani Is there a need for PRs on PG16 when it is already merged in master(which is PG16 now)?

@jrgemignani
Copy link
Contributor Author

@jrgemignani Is there a need for PRs on PG16 when it is already merged in master(which is PG16 now)?

Yes. I'm going to start the release process for PG16 -> PG11. So, they need all need to be at the same point.

@MuhammadTahaNaveed MuhammadTahaNaveed merged commit 585bc6e into apache:PG16 Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants