[Libre-soc-bugs] [Bug 1126] How to document new bugs/issues

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Mon Nov 13 20:40:03 GMT 2023


https://bugs.libre-soc.org/show_bug.cgi?id=1126

--- Comment #38 from Andrey Miroshnikov <andrey at technepisteme.xyz> ---
Finally got around to documenting the "I'm doing..." procedure, see here:
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=09d4356bdc5775c5e136b2760a584a159efb7aaf
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=583a0852053dde49ffadf56f629729c3fada3228

https://libre-soc.org/HDL_workflow/libresoc_bug_process/


(In reply to Luke Kenneth Casson Leighton from comment #37)
> hmmm just a thought, these are actually better done as TODO/DONE in comment
> #0
> otherwise new additions mix in with completed ones.
Modified comment #0.

> 
> plus: how do you know which ones are done and which are not?
Read the comment history hahaha (yes, I know, this is unsustainable, which is
why I followed your suggestion).

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the libre-soc-bugs mailing list