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

Include instructions for lldb-dap #112

Merged
merged 1 commit into from
Jul 4, 2024
Merged

Include instructions for lldb-dap #112

merged 1 commit into from
Jul 4, 2024

Conversation

skittishdev
Copy link
Contributor

Add an example for how to use lldb-dap

I spent a non-trivial amount of time trying to figure this out, and hope some one else can benefit from not having to figure this out themselves.

Add an example for how to use lldb-dap
@svaante
Copy link
Owner

svaante commented Jun 6, 2024

As I merged your other changes I believe that I need FSF copyright assignment as this + bb688ed is AFAIK legally significant

@skittishdev
Copy link
Contributor Author

@svaante,
I did sign and submit the copyright assignment a few weeks ago, but I haven't heard back yet. Will update this PR when I have more info.

@svaante svaante closed this in 54e160e Jun 30, 2024
@skittishdev
Copy link
Contributor Author

Hey,
I finally have my assignment. What next from here?

@skittishdev
Copy link
Contributor Author

Oh, looks like this PR was closed. Should I submit a new one?

@svaante
Copy link
Owner

svaante commented Jul 4, 2024

I closed it by accident :face_palm: @skittishdev

@svaante svaante reopened this Jul 4, 2024
@svaante svaante merged commit 4f5a9c0 into svaante:master Jul 4, 2024
1 check failed
@svaante
Copy link
Owner

svaante commented Jul 4, 2024

Thank you for your contribution 👍

@skittishdev
Copy link
Contributor Author

Awesome! Thank you so much!

@skittishdev skittishdev deleted the patch-2 branch July 4, 2024 17:15
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