Skip to content

Commit db4cfc6

Browse files
committed
link: we discussed what would need to happen in order to merge the fork of Bloop back inline
Signed-off-by: Josh Soref <[email protected]>
1 parent b8423da commit db4cfc6

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

blog/_posts/2023-04-11-march-2023-scala-tooling-summit.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -332,9 +332,8 @@ and comments about how it works, and questions about why it works a certain way.
332332
Some of the answers to these questions has led scala-cli to fork Bloop resulting
333333
in 2 bloop servers often running on a user’s machine if they are a Metals user.
334334
In order to combat this and provide a smoother Bloop experience for all users,
335-
we discussed what would need to happen in order to merge the fork of Bloop back
336-
inline. You can follow a thread on this effort
337-
[here](https://github.com/VirtusLab/scala-cli/issues/1971).
335+
[we discussed what would need to happen in order to merge the fork of Bloop back
336+
inline](https://github.com/VirtusLab/scala-cli/issues/1971).
338337

339338
## What comes next?
340339

0 commit comments

Comments
 (0)