From 3a72ce9d1248eb6e49647a4c431404ad2195385c Mon Sep 17 00:00:00 2001 From: Christopher Faylor Date: Sun, 5 Dec 2004 02:30:20 +0000 Subject: [PATCH] minor cleanup --- winsup/cygwin/ansi.sgml | 2 +- winsup/cygwin/how-vfork-works.txt | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/winsup/cygwin/ansi.sgml b/winsup/cygwin/ansi.sgml index d6a41ab31..4bce1d360 100644 --- a/winsup/cygwin/ansi.sgml +++ b/winsup/cygwin/ansi.sgml @@ -56,4 +56,4 @@ localeconv, setlocale, va_arg, va_end, va_start - \ No newline at end of file + diff --git a/winsup/cygwin/how-vfork-works.txt b/winsup/cygwin/how-vfork-works.txt index 7148366db..f249dab61 100644 --- a/winsup/cygwin/how-vfork-works.txt +++ b/winsup/cygwin/how-vfork-works.txt @@ -28,8 +28,8 @@ the result of a vfork and closes the extra file handles. This all relies on the fact that the child in a vfork call can affect just about everything in the parent except for the parent's fds. -The assumption is that a vfork is always just used as a method for -starting a program. +The assumption is that a vfork is always just used as a method for +starting a program. The assumption is also that all of this is much faster than the slow method that cygwin uses to implement fork().