Skip to content

fix: back out py-peer changes#235

Merged
dhuseby merged 1 commit intolibp2p:mainfrom
dhuseby:back-out-py-peer-changes
Feb 27, 2025
Merged

fix: back out py-peer changes#235
dhuseby merged 1 commit intolibp2p:mainfrom
dhuseby:back-out-py-peer-changes

Conversation

@dhuseby
Copy link
Copy Markdown
Collaborator

@dhuseby dhuseby commented Feb 27, 2025

Signed-off-by: Dave Grantham dwg@linuxprogrammer.org

Backing out the recent py-peer and workshop changes. This is moving to new branches called py-peer-development and workshop-development

Signed-off-by: Dave Grantham <dwg@linuxprogrammer.org>
@dhuseby
Copy link
Copy Markdown
Collaborator Author

dhuseby commented Feb 27, 2025

@p-shahi @2color @pacrob @seetadev

@p-shahi is correct that we should do this development in a branch before merging to main. This PR backs out the recent py-peer and workshop changes. I will create branches and PR to track the development work in.

@dhuseby dhuseby changed the title back out py-peer changes fix: back out py-peer changes Feb 27, 2025
@dhuseby dhuseby requested review from 2color and p-shahi February 27, 2025 04:21
@dhuseby dhuseby merged commit b83b67f into libp2p:main Feb 27, 2025
@dhuseby dhuseby deleted the back-out-py-peer-changes branch February 27, 2025 20:03
dozyio pushed a commit to dozyio/universal-connectivity that referenced this pull request Sep 7, 2025
Signed-off-by: Dave Grantham <dwg@linuxprogrammer.org>
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.

3 participants