You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
53 lines
2.5 KiB
53 lines
2.5 KiB
8 months ago
|
From 380f7af4fb00d692132b38999813fd9023e14c81 Mon Sep 17 00:00:00 2001
|
||
|
|
From: Jan Macku <jamacku@redhat.com>
|
||
|
|
Date: Thu, 10 Aug 2023 15:25:22 +0200
|
||
|
|
Subject: [PATCH] docs: link downstream CONTRIBUTING in README
|
||
|
|
|
||
|
|
This should increase the visibility of the downstream CONTRIBUTING.
|
||
|
|
|
||
|
|
Also fix some wording and update links.
|
||
|
|
|
||
|
|
rhel-only
|
||
|
|
|
||
|
|
Related: #2179309
|
||
|
|
---
|
||
|
|
CONTRIBUTING.md | 4 ++--
|
||
|
|
README.md | 2 +-
|
||
|
|
2 files changed, 3 insertions(+), 3 deletions(-)
|
||
|
|
|
||
|
|
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
|
||
|
|
index 1de2b88995..bd17067be2 100644
|
||
|
|
--- a/CONTRIBUTING.md
|
||
|
|
+++ b/CONTRIBUTING.md
|
||
|
|
@@ -17,7 +17,7 @@ flowchart LR
|
||
|
|
|
||
|
|
## Filing issues
|
||
|
|
|
||
|
|
-When you find an issue with systemd used in CentOS Stream or RHEL, please file an issue in [Jira ticket system](https://issues.redhat.com/secure/CreateIssueDetails!init.jspa?pid=12332745&issuetype=1&components=12380515).
|
||
|
|
+When you find an issue with systemd used in **CentOS Stream** or **RHEL**, please file an issue in Red Hat [Jira ticket system](https://issues.redhat.com/secure/CreateIssueDetails!init.jspa?pid=12332745&issuetype=1&components=12380515&priority=10300).
|
||
|
|
|
||
|
|
GitHub Issues are not supported tracking system. If your issue is reproducible using the latest upstream version of systemd, please consider creating [upstream issue](https://github.com/systemd/systemd/issues/new/choose).
|
||
|
|
|
||
|
|
@@ -51,7 +51,7 @@ Each commit has to reference the relevant approved systemd issue (see: [Filling
|
||
|
|
- **Related** for commits related to the referenced issue, but they don't fix it. Usually, tests and documentation.
|
||
|
|
- **Reverts** for commits that reverts previously merged commit
|
||
|
|
|
||
|
|
-When referencing issues, use following structure: `<keyword>: <issue ID>`. See the example below:
|
||
|
|
+When referencing issues, use the following structure: `<keyword>: <issue ID>`. See the example below:
|
||
|
|
|
||
|
|
```md
|
||
|
|
doc: Fix TYPO
|
||
|
|
diff --git a/README.md b/README.md
|
||
|
|
index a57566834c..2e02350299 100644
|
||
|
|
--- a/README.md
|
||
|
|
+++ b/README.md
|
||
|
|
@@ -17,7 +17,7 @@ Consult our [NEWS file](../master/NEWS) for information about what's new in the
|
||
|
|
|
||
|
|
Please see the [HACKING file](../master/doc/HACKING) for information how to hack on systemd and test your modifications.
|
||
|
|
|
||
|
|
-Please see our [Contribution Guidelines](../master/.github/CONTRIBUTING.md) for more information about filing GitHub Issues and posting GitHub Pull Requests.
|
||
|
|
+Please see our [Contribution Guidelines](CONTRIBUTING.md) for more information about filing GitHub Issues and posting GitHub Pull Requests.
|
||
|
|
|
||
|
|
When preparing patches for systemd, please follow our [Coding Style Guidelines](../master/doc/CODING_STYLE).
|
||
|
|
|