X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=HDL_workflow.mdwn;h=8e3472ffa19d44f09e8a02bb966384a27dc95dd7;hb=b4415717f8b444e7ffa5d4ffbf84f3c9889a8a26;hp=2e3dd9b4253807183b21841eb02a66e1ea13ae72;hpb=0fc59ca861e57038f963d5bc36d05e050741523e;p=libreriscv.git

diff --git a/HDL_workflow.mdwn b/HDL_workflow.mdwn
index 2e3dd9b42..8e3472ffa 100644
--- a/HDL_workflow.mdwn
+++ b/HDL_workflow.mdwn
@@ -341,7 +341,7 @@ relevant unit tests pass 100%.  This ensures that people's work does not
 get "lost" or isolated and out of touch due to major branch diversion,
 and that people communicate and coordinate with each other.
 
-This is not a hard rule: under special cirmstances branches can be useful.
+This is not a hard rule: under special circumstances branches can be useful.
 They should not however be considered "routine".
 
 For guidance on when branches are appropriate,
@@ -1304,6 +1304,11 @@ to me, because my background is in hardware not software engineering.
 
 # Task management guidelines
 
+* New guide for RfP submission (in-progress):
+[[HDL_workflow/rfp_submission_guide]]
+
+(This section needs to be compared with [[HDL_workflow/libresoc_bug_process]])
+
 1. Create the task in appropriate "Product" section with appropriate
   "Component" section. Most code tasks generally use "Libre-SOC's
   first SOC".