In the past most resolved bug reports contained links to little snippets of code which enabled non-programmers like myself to gain some insight into what was fixed, and occasionally to what else it might affect. These seem to have disappeared. Is there any simple way to access this information, given the reference numbers for the commits? Or is it now confidential?
-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum has become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
Diffs in bug reports
- Thread starter rogerh
- Start date
- Status
D
dlavigne
Guest
AFAIK, it's up to the developer to remember to link in the commit message when they resolve the bug...
The commits themselves are archived in several places. You can subscribe to the http://lists.freenas.org/pipermail/freenas-commit/ mailing list (or subscribe to it in gmane at http://dir.gmane.org/gmane.os.freenas.scm). Or you can click commits at https://github.com/freenas/freenas. Note that both the mailing list and gmane follow the master branch whereas at github you can click the "branch: master" drop-down to see other branches (such as stable (in an SU) or the 10 branch).
The commits themselves are archived in several places. You can subscribe to the http://lists.freenas.org/pipermail/freenas-commit/ mailing list (or subscribe to it in gmane at http://dir.gmane.org/gmane.os.freenas.scm). Or you can click commits at https://github.com/freenas/freenas. Note that both the mailing list and gmane follow the master branch whereas at github you can click the "branch: master" drop-down to see other branches (such as stable (in an SU) or the 10 branch).
- Status
