10.0
10.0-rc1
10.1
10.1-rc1
11.0
11.0-rc1
11.0-rc2
11.0-rc3
11.1
11.1-rc1
11.2
11.2-rc1
11.3
11.3-rc1
12.0
12.0-rc1
12.1
12.1-rc1
6.0
6.1
6.1.1
6.3
6.4
6.5
6.6
6.7
6.8
7.0
7.1
7.2
7.3
7.4
7.5
7.5-systemd
7.6
7.6-systemd
7.7
7.7-systemd
7.8
7.8-systemd
7.9
7.9-systemd
8.0
8.1
8.2
8.3
8.4
9.0
9.1
arm
bdubbs/gcc13
ml-11.0
multilib
renodr/libudev-from-systemd
s6-init
trunk
v4_0
v4_1
v5_0
v5_1
v5_1_1
xry111/arm64
xry111/arm64-12.0
xry111/clfs-ng
xry111/lfs-next
xry111/loongarch
xry111/loongarch-12.0
xry111/loongarch-12.1
xry111/mips64el
xry111/pip3
xry111/rust-wip-20221008
xry111/update-glibc
| Line | |
|---|
| 1 | <sect2><title>Contents of Patch-&patch-contversion;</title>
|
|---|
| 2 |
|
|---|
| 3 | <sect3><title>Program Files</title>
|
|---|
| 4 | <para>patch</para></sect3>
|
|---|
| 5 |
|
|---|
| 6 | <sect3><title>Descriptions</title>
|
|---|
| 7 |
|
|---|
| 8 | <sect4><title>patch</title>
|
|---|
| 9 | <para>The patch program modifies a file according to a patch file. A patch
|
|---|
| 10 | file usually is a list created by the diff program that contains
|
|---|
| 11 | instructions on how an original file needs to be modified. Patch is used
|
|---|
| 12 | a lot for source code patches since it saves time and space. Imagine
|
|---|
| 13 | a package that is 1MB in size. The next version of that package
|
|---|
| 14 | only has changes in two files of the first version. It can be shipped as an
|
|---|
| 15 | entirely new package of 1MB or just as a patch file of 1KB which will
|
|---|
| 16 | update the first version to make it identical to the second version. So
|
|---|
| 17 | if the first version was downloaded already, a patch file avoids
|
|---|
| 18 | a second large download.</para></sect4>
|
|---|
| 19 |
|
|---|
| 20 | </sect3>
|
|---|
| 21 |
|
|---|
| 22 | </sect2>
|
|---|
| 23 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
