commit 72356abe447ac95f9bc663bae0d8e394c8949ce6
parent a19b2a932e39944c360dac18aabd7d5c61deb368
Author: Sebastian <sebastian@sebsite.pw>
Date: Sat, 9 Dec 2023 21:14:18 -0500
docs/rfc-template: wrap at 72 columns
This was wrapped at 80 columns, which isn't correct for email. The
section headers were also centered for 80 columns, so within emails they
were off-center to the right. The headers are now also aligned with
spaces rather than a mixture of tabs and spaces.
Signed-off-by: Sebastian <sebastian@sebsite.pw>
Diffstat:
1 file changed, 22 insertions(+), 21 deletions(-)
diff --git a/docs/rfc-template.txt b/docs/rfc-template.txt
@@ -1,41 +1,42 @@
- RFC SUMMARY
+ RFC SUMMARY
Free-form brief summary of the RFC's goals, 1-2 paragraphs in length.
- LANGUAGE IMPLICATIONS
+ LANGUAGE IMPLICATIONS
Enumerate proposed language changes in this section, if any.
Put "None" here if there are no language implications.
- STANDARD LIBRARY IMPLICATIONS
+ STANDARD LIBRARY IMPLICATIONS
-Enumerate proposed standard library changes in this section, if any. Focus on
-breaking changes to the standard library's API over implementation details,
-unless implementation details are particularly important.
+Enumerate proposed standard library changes in this section, if any.
+Focus on breaking changes to the standard library's API over
+implementation details, unless implementation details are particularly
+important.
Put "None" here if there are no standard library implications.
- ECOSYSTEM IMPLICATIONS
+ ECOSYSTEM IMPLICATIONS
-Include considerations for the broader Hare ecosystem here, such as a survey
-estimating how many third-party codebases will be affected and how difficult it
-will be to implement the changes. If necessary, make a plan for alleviating the
-impact, such as automated migration tools (e.g. a sed script, or a dedicated
-tool for more complex migrations).
+Include considerations for the broader Hare ecosystem here, such as a
+survey estimating how many third-party codebases will be affected and
+how difficult it will be to implement the changes. If necessary, make a
+plan for alleviating the impact, such as automated migration tools (e.g.
+a sed script, or a dedicated tool for more complex migrations).
-Put "None" here if there are no ecosystem implications (though in this case, why
-is there an RFC for it?).
+Put "None" here if there are no ecosystem implications (though in this
+case, why is there an RFC for it?).
- EXAMPLE CODE
+ EXAMPLE CODE
-Include in this section samples of example code as it will appear under this
-RFC's proposed changes. This section is mandatory.
+Include in this section samples of example code as it will appear under
+this RFC's proposed changes. This section is mandatory.
- RELATED RFCS
+ RELATED RFCS
-Include a link to relevant RFCs (such as the prior version) on the hare-rfc
-web archives, as well as a brief summary of changes from that version or the
-reason why this RFC is relevant.
+Include a link to relevant RFCs (such as the prior version) on the
+hare-rfc web archives, as well as a brief summary of changes from that
+version or the reason why this RFC is relevant.
Put "None" here if there are no relevant RFCs.
