From c258333f272f18fdeb70dd478f7f937f0c5d3ebf Mon Sep 17 00:00:00 2001 From: Andrey Miroshnikov Date: Mon, 13 Nov 2023 19:30:22 +0000 Subject: [PATCH] 80 chars per line fix --- HDL_workflow/libresoc_bug_process.mdwn | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/HDL_workflow/libresoc_bug_process.mdwn b/HDL_workflow/libresoc_bug_process.mdwn index a2ddd65ac..336fdc216 100644 --- a/HDL_workflow/libresoc_bug_process.mdwn +++ b/HDL_workflow/libresoc_bug_process.mdwn @@ -31,11 +31,13 @@ to keep an up-to-date list of their tasks. ##How to raise issues 1. Create a bug report. -2. Add in any links from the mailing list or IRC logs to the bug report for back tracking - (this is mandatory). Also fill in the URL field if there is a relevant wiki page. +2. Add in any links from the mailing list or IRC logs to the bug report for +back tracking (this is mandatory). Also fill in the URL field if there is a +relevant wiki page. 3. CC in relevant team members -4. make absolutely sure to fill in "blocks", "depends on" or "see also" so that the - bug is not isolated (otherwise bugs are too hard to find if isolated from everything else) +4. Make absolutely sure to fill in "blocks", "depends on" or "see also" so +that the bug is not isolated (otherwise bugs are too hard to find if isolated +from everything else) 5. Ping on IRC to say a bug has been created 6. Unless you know exactly which milestone to use, leave blank initially. This also applies when editing milestone, budget parent/child, toml fields. See -- 2.30.2