From 51b4c035919497f474ce46dcbdac1d2f3fd18a84 Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Sun, 2 Feb 2014 21:50:57 -0700 Subject: [PATCH] Porting/Glossary: Entries should start with \t not blanks For otherwise, they get turned into verbatim lines. I don't know where to document this. --- Porting/Glossary | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/Porting/Glossary b/Porting/Glossary index 62b0560..f8fc4e4 100644 --- a/Porting/Glossary +++ b/Porting/Glossary @@ -4913,17 +4913,17 @@ targetarch (Cross.U): If not, this will be empty. targetdir (Cross.U): - This variable contains a path that will be created on the target - host using targetmkdir, and then used to copy the cross-compiled - executables to. Defaults to '/tmp' if not set. + This variable contains a path that will be created on the target + host using targetmkdir, and then used to copy the cross-compiled + executables to. Defaults to '/tmp' if not set. targetenv (Cross.U): - If cross-compiling, this variable can be used to modify the - environment on the target system. - However, how and where it's used, and even if it's used at all, is - entirely dependent on both the transport mechanism (targetrun) and - what the target system is. Unless the relevant documentation says - otherwise, it is genereally not useful. + If cross-compiling, this variable can be used to modify the + environment on the target system. + However, how and where it's used, and even if it's used at all, is + entirely dependent on both the transport mechanism (targetrun) and + what the target system is. Unless the relevant documentation says + otherwise, it is genereally not useful. targethost (Cross.U): This variable contains the name of a separate host machine that -- 2.7.4