aboutsummaryrefslogtreecommitdiffstats
path: root/appendixa/patch-desc.xml
diff options
context:
space:
mode:
authorThomas Balu Walter <tw@itreff.de>2001-03-16 18:09:38 +0000
committerThomas Balu Walter <tw@itreff.de>2001-03-16 18:09:38 +0000
commit7d90bd3ad9a841e20e060dab886397b6fc8c968e (patch)
tree86972d95e26c031040babcde5fee49d543f17ae0 /appendixa/patch-desc.xml
parentaff91c471bc146b4ac83faec877ca0b4f71d2782 (diff)
Some more You-Fixes
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@331 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'appendixa/patch-desc.xml')
-rw-r--r--appendixa/patch-desc.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/appendixa/patch-desc.xml b/appendixa/patch-desc.xml
index 410df67d2..c59f6b836 100644
--- a/appendixa/patch-desc.xml
+++ b/appendixa/patch-desc.xml
@@ -14,12 +14,12 @@ The patch program modifies a file according to a patch file. A patch
file usually is a list created by the diff program that contains
instructions on how an original file needs to be modified. Patch is used
a lot for source code patches since it saves time and space. Imagine
-you have a package that is 1MB in size. The next version of that package
-only has changes in two files of the first version. You can ship an
-entirely new package of 1MB or provide a patch file of 1KB which will
+a package that is 1MB in size. The next version of that package
+only has changes in two files of the first version. It can be shipped as an
+entirely new package of 1MB or just as a patch file of 1KB which will
update the first version to make it identical to the second version. So
-if you have downloaded the first version already, a patch file can
-save you a second large download.
+if the first version was downloaded already, a patch file avoids
+a second large download.
</para>
</sect2>