Skip to content

Commit 8fd4dd1

Browse files
wesleywiserdavidtwco
authored andcommitted
Fix long lines
1 parent 0322fb4 commit 8fd4dd1

File tree

1 file changed

+17
-8
lines changed

1 file changed

+17
-8
lines changed

src/licenses.md

+17-8
Original file line numberDiff line numberDiff line change
@@ -6,33 +6,42 @@ Detailed licensing information is available in the [COPYRIGHT document](https://
66

77
## Guidelines for reviewers
88

9-
In general, reviewers need to be looking not only for the code quality of contributions but also that they are properly licensed.
10-
We have some tips below for things to look out for when reviewing, but if you ever feel uncertain as to whether some code might be properly licensed, err on the safe side — reach out to the Council or Compiler Team Leads for feedback!
9+
In general, reviewers need to be looking not only for the code quality of contributions but also
10+
that they are properly licensed.
11+
We have some tips below for things to look out for when reviewing, but if you ever feel uncertain
12+
as to whether some code might be properly licensed, err on the safe side — reach out to the Council
13+
or Compiler Team Leads for feedback!
1114

1215
Things to watch out for:
1316

1417
- The PR author states that they copied, ported, or adapted the code from some other source.
15-
- There is a comment in the code pointing to a webpage or describing where the algorithm was taken from.
18+
- There is a comment in the code pointing to a webpage or describing where the algorithm was taken
19+
from.
1620
- The algorithm or code pattern seems like it was likely copied from somewhere else.
1721
- When adding new dependencies, double check the dependency's license.
1822

19-
In all of these cases, we will want to check that source to make sure it it is licensed in a way that is compatible with Rust’s license.
23+
In all of these cases, we will want to check that source to make sure it it is licensed in a way
24+
that is compatible with Rust’s license.
2025

2126
Examples
2227

23-
- Porting C code from a GPL project, like GNU binutils, is not allowed. That would require rust itself to be licensed under the GPL.
28+
- Porting C code from a GPL project, like GNU binutils, is not allowed. That would require Rust
29+
itself to be licensed under the GPL.
2430
- Copying code from an algorithms text book may be allowed, but some algorithms are patented.
2531

2632
## Porting
2733

28-
Contributions to rustc, especially around platform and compiler intrinsics, often include porting over work from other projects, mainly LLVM and GCC.
34+
Contributions to rustc, especially around platform and compiler intrinsics, often include porting
35+
over work from other projects, mainly LLVM and GCC.
2936

3037
Some general rules apply:
3138

3239
- Copying work needs to adhere to the original license
3340
- This applies to direct copy & paste
3441
- This also applies to code you looked at and ported
3542

36-
In general, taking inspiration from other codebases is fine, but please exercise caution when porting code.
43+
In general, taking inspiration from other codebases is fine, but please exercise caution when
44+
porting code.
3745

38-
Ports of full libraries (e.g. C libraries shipped with LLVM) must keep the license of the original library.
46+
Ports of full libraries (e.g. C libraries shipped with LLVM) must keep the license of the original
47+
library.

0 commit comments

Comments
 (0)