Skip to content

Conversation

jrudolph
Copy link
Contributor

@jrudolph jrudolph commented Mar 6, 2023

No description provided.

@jrudolph jrudolph force-pushed the clear-some-warnings branch 2 times, most recently from ee51463 to 7a7ef21 Compare March 6, 2023 14:07
@mdedetrich
Copy link
Contributor

@jrudolph Should this be reviewed?

@He-Pin
Copy link
Member

He-Pin commented Jan 21, 2024

@jrudolph would you mind me merge your changes and push it,or you will do it sometime later?

@He-Pin
Copy link
Member

He-Pin commented Sep 9, 2024

@mdedetrich @pjfanning I think we can continue this and includes it in 1.1.0

@pjfanning
Copy link
Member

Some of them are fixed already. I think we can continue dev on Pekko HTTP for a few more days but the aim is to do a 1.1.0 release when Pekkko 1.1.1 is released.

@mdedetrich
Copy link
Contributor

Some of them are fixed already. I think we can continue dev on Pekko HTTP for a few more days but the aim is to do a 1.1.0 release when Pekkko 1.1.1 is released.

Just re-iterating that we shouldn't do a release of Pekko Http until #590 (review) is addressed

# Conflicts:
#	http-core/src/main/scala/org/apache/pekko/http/impl/engine/rendering/RenderSupport.scala
#	http-core/src/main/scala/org/apache/pekko/http/scaladsl/model/HttpEntity.scala
#	http-core/src/test/scala/org/apache/pekko/http/impl/engine/client/LowLevelOutgoingConnectionSpec.scala
#	http-core/src/test/scala/org/apache/pekko/http/impl/model/parser/HttpHeaderSpec.scala
#	project/Common.scala
@jrudolph jrudolph force-pushed the clear-some-warnings branch from 7a7ef21 to 79ca0ad Compare October 10, 2025 12:25
@jrudolph
Copy link
Contributor Author

I guess, not worth pursuing further, right now.

@jrudolph jrudolph closed this Oct 10, 2025
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.

4 participants