#
31de159f |
| 24-Jun-2020 |
Adriana Kobylak <anoo@us.ibm.com> |
Move code-update directory to architecture It makes sense to have the code-update documents under architecture instead of at the top directory. Change-Id: Ie850a12adf0507307ca29
Move code-update directory to architecture It makes sense to have the code-update documents under architecture instead of at the top directory. Change-Id: Ie850a12adf0507307ca29edddaaff67756c35029 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
show more ...
|
#
c7c7c866 |
| 06-Nov-2018 |
Joel Stanley <joel@jms.id.au> |
userguide: update path to code-update This was moved in c4c7f4055387 ("Moved host code update to own doc") but no one updated the makefile. Change-Id: I2b0b3aad6d2436c9cb207a4fa
userguide: update path to code-update This was moved in c4c7f4055387 ("Moved host code update to own doc") but no one updated the makefile. Change-Id: I2b0b3aad6d2436c9cb207a4faeff7468e54a5b2a Signed-off-by: Joel Stanley <joel@jms.id.au>
show more ...
|
#
8b80cb60 |
| 25-May-2016 |
Jeremy Kerr <jk@ozlabs.org> |
userguide: Don't use pandoc for final tex output When using pandoc to create the main .tex document, we lose all styles and formatting information in the main userguide doc. Thi
userguide: Don't use pandoc for final tex output When using pandoc to create the main .tex document, we lose all styles and formatting information in the main userguide doc. This change reverts commit bba5b1817e89bd63766e2bb91d406130f027fcaf, and adds the \tighlist macro that was required by that change. Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
show more ...
|
#
cef0ec7f |
| 18-May-2016 |
nkskjames <nkskjames@gmail.com> |
Merge pull request #21 from hramasub/logman RFC on the OBMC Service Interface.
|
#
a7297431 |
| 04-May-2016 |
Jeremy Kerr <jk@ozlabs.org> |
Add infrastructure for User Guide This change adds a little infrastructure for creating an OpenBMC User's Guide, from the user-related documents in markdown. Signed-off-by: Jere
Add infrastructure for User Guide This change adds a little infrastructure for creating an OpenBMC User's Guide, from the user-related documents in markdown. Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
show more ...
|