diff options
| author | Gerard Beekmans <gerard@linuxfromscratch.org> | 2001-02-15 15:26:52 +0000 |
|---|---|---|
| committer | Gerard Beekmans <gerard@linuxfromscratch.org> | 2001-02-15 15:26:52 +0000 |
| commit | b08f4096533577934b885fa9df41d3881d141612 (patch) | |
| tree | 8e5ffc0ba65ac34d97cd6a896d33b85a897a6da8 /appendixa/patch-desc.xml | |
| parent | ad08014624938a3a3bfd1b44e8b27d02c7b06dd8 (diff) | |
Initial XML commit
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@174 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'appendixa/patch-desc.xml')
| -rw-r--r-- | appendixa/patch-desc.xml | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/appendixa/patch-desc.xml b/appendixa/patch-desc.xml new file mode 100644 index 000000000..410df67d2 --- /dev/null +++ b/appendixa/patch-desc.xml @@ -0,0 +1,26 @@ +<sect2> +<title>Contents</title> + +<para> +The Patch package contains the patch program. +</para> + +</sect2> + +<sect2><title>Description</title> + +<para> +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 +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. +</para> + +</sect2> + |