-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
2024 Meetings are Missing (although I appreciate the 2023 races!) #18
Comments
Hello, |
Thanks Bruno!
Sorry about all of the calls I’ve been making this morning while updating my app to handle the 2024 practice I see you added!
I owe you a coffee…or 6.
Maybe when I’m in Paris this May.
Thanks,
Harrison
…On Feb 29, 2024 at 09:37 -0500, Bruno Godefroy ***@***.***>, wrote:
Hello,
For now, only past events are provided by the API.
Future events will be added soon!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hello,
No worries for your API calls!
The project is still very early and I'm happy to see the first users using it.
I would be happy to chat with you when you come to Paris!
Best,
Bruno
Sent: Thursday, February 29, 2024 at 3:39 PM
From: "hwpaige" ***@***.***>
To: "br-g/openf1" ***@***.***>
Cc: "Bruno Godefroy" ***@***.***>, "State change" ***@***.***>
Subject: Re: [br-g/openf1] 2024 Meetings are Missing (although I appreciate the 2023 races!) (Issue #18)
Thanks Bruno!
Sorry about all of the calls I’ve been making this morning while updating my app to handle the 2024 practice I see you added!
I owe you a coffee…or 6.
Maybe when I’m in Paris this May.
Thanks,
Harrison
On Feb 29, 2024 at 09:37 -0500, Bruno Godefroy ***@***.***>, wrote:
Hello,
For now, only past events are provided by the API.
Future events will be added soon!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: