Skip to content

Conversation

@akoeplinger
Copy link
Member

This was a custom change added in da3d772 but we missed porting that to recent branches.

Given we've not even noticed until now and it just causes building a bit more tools I'd argue it's better to just remove this.

This was a custom change added in da3d772 but we missed porting that to recent branches.

Given we've not even noticed until now and it just causes building a bit more tools I'd argue it's better to just remove this.
@akoeplinger akoeplinger requested a review from radekdoulik July 4, 2024 13:22
@akoeplinger akoeplinger merged commit 01a05ca into dotnet/main-16.x Jul 9, 2024
@akoeplinger akoeplinger deleted the akoeplinger-patch-1 branch July 9, 2024 09:38
akoeplinger added a commit that referenced this pull request Jul 17, 2024
This was a custom change added in da3d772 but we missed porting that to recent branches.

Given we've not even noticed until now and it just causes building a bit more tools I'd argue it's better to just remove this.
radekdoulik pushed a commit that referenced this pull request Aug 16, 2024
This was a custom change added in da3d772 but we missed porting that to recent branches.

Given we've not even noticed until now and it just causes building a bit more tools I'd argue it's better to just remove this.
radekdoulik pushed a commit that referenced this pull request Sep 2, 2024
This was a custom change added in da3d772 but we missed porting that to recent branches.

Given we've not even noticed until now and it just causes building a bit more tools I'd argue it's better to just remove this.
radekdoulik pushed a commit that referenced this pull request Sep 12, 2024
This was a custom change added in da3d772 but we missed porting that to recent branches.

Given we've not even noticed until now and it just causes building a bit more tools I'd argue it's better to just remove this.
radekdoulik pushed a commit that referenced this pull request Sep 19, 2024
This was a custom change added in da3d772 but we missed porting that to recent branches.

Given we've not even noticed until now and it just causes building a bit more tools I'd argue it's better to just remove this.
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