[PATCH 2/5] formal/ppcmem: Avoid break-line after 'lines' in source

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>From 27111136894e2086427460036d1002179bd6aad2 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@xxxxxxxxx>
Date: Fri, 5 Aug 2016 07:24:29 +0900
Subject: [PATCH 2/5] formal/ppcmem: Avoid break-line after 'lines' in source

Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
 formal/ppcmem.tex | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/formal/ppcmem.tex b/formal/ppcmem.tex
index 8fb1dd9..cf637ad 100644
--- a/formal/ppcmem.tex
+++ b/formal/ppcmem.tex
@@ -133,8 +133,9 @@ in actual use.
 } \QuickQuizEnd
 
 Lines~8-17 are the lines of code for each process. A given process
-can have empty lines, as is the case for P0's line~11 and P1's lines
-12-17. Labels and branches are permitted, as demonstrated by the branch
+can have empty lines, as is the case for P0's line~11 and P1's
+lines~12-17.
+Labels and branches are permitted, as demonstrated by the branch
 on line~14 to the label on line~17. That said, too-free use of branches
 will expand the state space. Use of loops is a particularly good way to
 explode your state space.
-- 
1.9.1


--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux