From 35045a3e175866c8f4afceb1eec7d7378fa74d8d Mon Sep 17 00:00:00 2001 From: Seth Tisue Date: Thu, 17 Oct 2024 18:50:24 -0700 Subject: [PATCH] copyright 2024 --- NOTICE | 4 ++-- README.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/NOTICE b/NOTICE index 92d7557..f5f60fe 100644 --- a/NOTICE +++ b/NOTICE @@ -1,6 +1,6 @@ scala-collection-contrib -Copyright (c) 2017-2023 EPFL -Copyright (c) 2017-2023 Lightbend, Inc. +Copyright (c) 2017-2024 EPFL +Copyright (c) 2017-2024 Lightbend, Inc. Includes software developed at LAMP/EPFL (https://lamp.epfl.ch/) and diff --git a/README.md b/README.md index 7927e98..b9f2992 100644 --- a/README.md +++ b/README.md @@ -53,4 +53,4 @@ participating, please jump right in on issues and pull requests. scala-collection-contrib's merge policy is liberal: we're happy to merge most things here, without too much review, so that people can try them out. -There is now (as of October 2020) the [scala-library-next repo](https://github.com/scala/scala-library-next), which is where we decide what will actually be added to the next version of the Scala standard library. The standards for merging things there are much more conservative. +There is now (since 2020) the [scala-library-next repo](https://github.com/scala/scala-library-next), which is where we decide what will actually be added to the next version of the Scala standard library. The standards for merging things there are much more conservative.