Conversation
e97510c to
571180b
Compare
02b25cc to
3624ad9
Compare
timmiesmith
left a comment
There was a problem hiding this comment.
This looks good to me. I noticed that we're not consistent in the use of dates in the copyright notice. I'd prefer to see the years removed for simplicity, but if we need to keep them I've checked the oneAPI-spec repo to identify what the ranges should be for each file.
| @@ -0,0 +1,197 @@ | |||
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |||
There was a problem hiding this comment.
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |
| .. SPDX-FileCopyrightText: 2019-2025 Intel Corporation |
There was a problem hiding this comment.
I will update the copyrights in a subsequent PR.
| @@ -0,0 +1,309 @@ | |||
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |||
There was a problem hiding this comment.
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |
| .. SPDX-FileCopyrightText: 2019-2025 Intel Corporation |
Update year to the last time a PR touched the file.
| @@ -0,0 +1,113 @@ | |||
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |||
There was a problem hiding this comment.
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |
| .. SPDX-FileCopyrightText: 2019-2025 Intel Corporation |
Update year to the last time a PR touched the file.
| @@ -0,0 +1,243 @@ | |||
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |||
There was a problem hiding this comment.
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |
| .. SPDX-FileCopyrightText: 2019-2025 Intel Corporation |
| @@ -0,0 +1,457 @@ | |||
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |||
There was a problem hiding this comment.
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |
| .. SPDX-FileCopyrightText: 2019-2025 Intel Corporation |
| @@ -0,0 +1,1054 @@ | |||
| .. SPDX-FileCopyrightText: Contributors to the oneAPI Specification project. | |||
| .. | |||
There was a problem hiding this comment.
There is no mention of the Copyright year(s) here. Do we want to remove the years from the other files or add it here so that we are consistent?
| @@ -0,0 +1,53 @@ | |||
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |||
There was a problem hiding this comment.
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |
| .. SPDX-FileCopyrightText: 2019-2024 Intel Corporation |
documentation/specification/conf.py
Outdated
| @@ -0,0 +1,27 @@ | |||
| # SPDX-FileCopyrightText: 2019-2020 Intel Corporation | |||
| # | |||
There was a problem hiding this comment.
This seems to be the oldest file and doesn't mention years in the copyright notice. I think I'd prefer to remove it from the others to be consistent.
| @@ -0,0 +1,50 @@ | |||
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |||
There was a problem hiding this comment.
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |
| .. SPDX-FileCopyrightText: 2019-2024 Intel Corporation |
If we decide to keep years in the notice
| @@ -0,0 +1,30 @@ | |||
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |||
There was a problem hiding this comment.
| .. SPDX-FileCopyrightText: 2019-2022 Intel Corporation | |
| .. SPDX-FileCopyrightText: 2019-2025 Intel Corporation |
| oneDPL Specification | ||
| ==================== | ||
|
|
||
| This is the specification of |onedpl_long|, version 1.5. |
There was a problem hiding this comment.
I think we should mention that the history can be found at https://github.com/uxlfoundation/oneAPI-spec/, and that we are copying this as of a specific commit hash (15dd358db74b31dc9a5668b8127d872f4210ed3a).
There was a problem hiding this comment.
I will mention that in the commit message, as well as in the description of this PR which the commit message will refer to. I think that should be sufficient to track the history.
|
@timmiesmith @danhoeflinger My intent for this PR was to just copy the source files and do bare minimum necessary to add the spec into the doc tree, with other changes done in subsequent PRs. Maybe I should leave just the single "copy the files" commit here, making all other changes in a new PR. Update: I have done that. |
…ndation/oneAPI-spec/tree/main/source/elements/oneDPL/source, commit 0d9d8e993c3b077dad7922c8f3096d9dd5d938d0
3624ad9 to
b1afb07
Compare
|
Should we integrate the specification into the documentation tree, e.g. by adding it into https://github.com/uxlfoundation/oneDPL/blob/main/documentation/library_guide/guide_toc.rst or https://github.com/uxlfoundation/oneDPL/blob/main/documentation/index.rst? |
#2640 does this. |
Copy the oneDPL specification source files from https://github.com/uxlfoundation/oneAPI-spec/tree/main/source/elements/oneDPL/source, commit 0d9d8e993c3b077dad7922c8f3096d9dd5d938d0