From: John Ousterhout <ouster@cs.stanford.edu> Date: Tue, 19 May 2020 04:32:20 +0000 (-0700) Subject: Convert tabs to spaces in design doc templates X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1407c40250b1b7563c9927e63490971e4cdeb389;p=pintos-anon Convert tabs to spaces in design doc templates --- diff --git a/doc/filesys.tmpl b/doc/filesys.tmpl index db792bf..f3bd101 100644 --- a/doc/filesys.tmpl +++ b/doc/filesys.tmpl @@ -1,8 +1,8 @@ - +-------------------------+ - | CS 140 | - | PROJECT 4: FILE SYSTEMS | - | DESIGN DOCUMENT | - +-------------------------+ + +-------------------------+ + | CS 140 | + | PROJECT 4: FILE SYSTEMS | + | DESIGN DOCUMENT | + +-------------------------+ ---- GROUP ---- @@ -21,8 +21,8 @@ FirstName LastName <email@domain.example> >> preparing your submission, other than the Pintos documentation, course >> text, lecture notes, and course staff. - INDEXED AND EXTENSIBLE FILES - ============================ + INDEXED AND EXTENSIBLE FILES + ============================ ---- DATA STRUCTURES ---- @@ -60,8 +60,8 @@ FirstName LastName <email@domain.example> >> structure, and what advantages and disadvantages does your >> structure have, compared to a multilevel index? - SUBDIRECTORIES - ============== + SUBDIRECTORIES + ============== ---- DATA STRUCTURES ---- @@ -91,8 +91,8 @@ FirstName LastName <email@domain.example> >> B6: Explain why you chose to represent the current directory of a >> process the way you did. - BUFFER CACHE - ============ + BUFFER CACHE + ============ ---- DATA STRUCTURES ---- @@ -123,8 +123,8 @@ FirstName LastName <email@domain.example> >> C7: Describe a file workload likely to benefit from buffer caching, >> and workloads likely to benefit from read-ahead and write-behind. - SURVEY QUESTIONS - ================ + SURVEY QUESTIONS + ================ Answering these questions is optional, but it will help us improve the course in future quarters. Feel free to tell us anything you diff --git a/doc/threads.tmpl b/doc/threads.tmpl index b34b4e2..f87f464 100644 --- a/doc/threads.tmpl +++ b/doc/threads.tmpl @@ -1,9 +1,9 @@ - +--------------------+ - | CS 140 | - | PROJECT 1: THREADS | - | DESIGN DOCUMENT | - +--------------------+ - + +--------------------+ + | CS 140 | + | PROJECT 1: THREADS | + | DESIGN DOCUMENT | + +--------------------+ + ---- GROUP ---- >> Fill in the names and email addresses of your group members. @@ -21,8 +21,8 @@ FirstName LastName <email@domain.example> >> preparing your submission, other than the Pintos documentation, course >> text, lecture notes, and course staff. - ALARM CLOCK - =========== + ALARM CLOCK + =========== ---- DATA STRUCTURES ---- @@ -51,8 +51,8 @@ FirstName LastName <email@domain.example> >> A6: Why did you choose this design? In what ways is it superior to >> another design you considered? - PRIORITY SCHEDULING - =================== + PRIORITY SCHEDULING + =================== ---- DATA STRUCTURES ---- @@ -86,8 +86,8 @@ FirstName LastName <email@domain.example> >> B7: Why did you choose this design? In what ways is it superior to >> another design you considered? - ADVANCED SCHEDULER - ================== + ADVANCED SCHEDULER + ================== ---- DATA STRUCTURES ---- @@ -137,8 +137,8 @@ ticks A B C A B C to run >> type and/or a set of functions or macros to manipulate fixed-point >> numbers, why did you do so? If not, why not? - SURVEY QUESTIONS - ================ + SURVEY QUESTIONS + ================ Answering these questions is optional, but it will help us improve the course in future quarters. Feel free to tell us anything you diff --git a/doc/userprog.tmpl b/doc/userprog.tmpl index a489303..03c7fa0 100644 --- a/doc/userprog.tmpl +++ b/doc/userprog.tmpl @@ -1,8 +1,8 @@ - +--------------------------+ - | CS 140 | - | PROJECT 2: USER PROGRAMS | - | DESIGN DOCUMENT | - +--------------------------+ + +--------------------------+ + | CS 140 | + | PROJECT 2: USER PROGRAMS | + | DESIGN DOCUMENT | + +--------------------------+ ---- GROUP ---- @@ -21,8 +21,8 @@ FirstName LastName <email@domain.example> >> preparing your submission, other than the Pintos documentation, course >> text, lecture notes, and course staff. - ARGUMENT PASSING - ================ + ARGUMENT PASSING + ================ ---- DATA STRUCTURES ---- @@ -44,8 +44,8 @@ FirstName LastName <email@domain.example> >> and arguments. In Unix-like systems, the shell does this >> separation. Identify at least two advantages of the Unix approach. - SYSTEM CALLS - ============ + SYSTEM CALLS + ============ ---- DATA STRUCTURES ---- @@ -111,8 +111,8 @@ FirstName LastName <email@domain.example> >> B11: The default tid_t to pid_t mapping is the identity mapping. >> If you changed it, what advantages are there to your approach? - SURVEY QUESTIONS - ================ + SURVEY QUESTIONS + ================ Answering these questions is optional, but it will help us improve the course in future quarters. Feel free to tell us anything you diff --git a/doc/vm.tmpl b/doc/vm.tmpl index 5733643..9e6a9a5 100644 --- a/doc/vm.tmpl +++ b/doc/vm.tmpl @@ -1,8 +1,8 @@ - +---------------------------+ - | CS 140 | - | PROJECT 3: VIRTUAL MEMORY | - | DESIGN DOCUMENT | - +---------------------------+ + +---------------------------+ + | CS 140 | + | PROJECT 3: VIRTUAL MEMORY | + | DESIGN DOCUMENT | + +---------------------------+ ---- GROUP ---- @@ -21,8 +21,8 @@ FirstName LastName <email@domain.example> >> preparing your submission, other than the Pintos documentation, course >> text, lecture notes, and course staff. - PAGE TABLE MANAGEMENT - ===================== + PAGE TABLE MANAGEMENT + ===================== ---- DATA STRUCTURES ---- @@ -49,8 +49,8 @@ FirstName LastName <email@domain.example> >> A5: Why did you choose the data structure(s) that you did for >> representing virtual-to-physical mappings? - PAGING TO AND FROM DISK - ======================= + PAGING TO AND FROM DISK + ======================= ---- DATA STRUCTURES ---- @@ -103,8 +103,8 @@ FirstName LastName <email@domain.example> >> where your design falls along this continuum and why you chose to >> design it this way. - MEMORY MAPPED FILES - =================== + MEMORY MAPPED FILES + =================== ---- DATA STRUCTURES ---- @@ -130,8 +130,8 @@ FirstName LastName <email@domain.example> >> implementation either does or does not share much of the code for >> the two situations. - SURVEY QUESTIONS - ================ + SURVEY QUESTIONS + ================ Answering these questions is optional, but it will help us improve the course in future quarters. Feel free to tell us anything you