From: Ben Pfaff <blp@cs.stanford.edu>
Date: Sun, 2 Jan 2005 00:08:17 +0000 (+0000)
Subject: Remove redundant footnote.
X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=87762f2bed6156b9fd233f4c20d5fdd0012634f2;p=pintos-anon

Remove redundant footnote.
---

diff --git a/doc/vm.texi b/doc/vm.texi
index 599539b..90d407d 100644
--- a/doc/vm.texi
+++ b/doc/vm.texi
@@ -256,9 +256,7 @@ It is impossible to predict how large the stack will grow at compile
 time, so we must allocate pages as necessary.  You should only allocate
 additional pages if they ``appear'' to be stack accesses.  You must
 devise a heuristic that attempts to distinguish stack accesses from
-other accesses.@footnote{You might find it useful to know that the
-80@var{x}86 instruction @code{pusha} pushes all 8 registers (32 bytes)
-on the stack at once.}  Document and explain the heuristic in your
+other accesses.  Document and explain the heuristic in your
 design documentation.
 
 The first stack page need not be loaded lazily.  You can initialize it