1
0
mirror of https://github.com/moparisthebest/wget synced 2024-07-03 16:38:41 -04:00

Improve accuracy in documentation regarding -nd with -r or -p. Bug #21509.

This commit is contained in:
Micah Cowan 2009-06-12 17:56:12 -07:00
parent 1975b2f8f5
commit dc7f8ea8d2
2 changed files with 22 additions and 16 deletions

View File

@ -1,3 +1,8 @@
2009-06-12 Micah Cowan <micah@cowan.name>
* wget.texi (Download Options): More accuracy on what happens when
-nd is used with -r or -p.
2009-06-11 Micah Cowan <micah@cowan.name>
* wget.texi (Contributors): Added Xin Zou, Benjamin Wolsley, and

View File

@ -582,23 +582,24 @@ behavior depends on a few options, including @samp{-nc}. In certain
cases, the local file will be @dfn{clobbered}, or overwritten, upon
repeated download. In other cases it will be preserved.
When running Wget without @samp{-N}, @samp{-nc}, @samp{-r}, or @samp{p},
downloading the same file in the same directory will result in the
original copy of @var{file} being preserved and the second copy being
named @samp{@var{file}.1}. If that file is downloaded yet again, the
third copy will be named @samp{@var{file}.2}, and so on. When
@samp{-nc} is specified, this behavior is suppressed, and Wget will
refuse to download newer copies of @samp{@var{file}}. Therefore,
``@code{no-clobber}'' is actually a misnomer in this mode---it's not
clobbering that's prevented (as the numeric suffixes were already
preventing clobbering), but rather the multiple version saving that's
prevented.
When running Wget without @samp{-N}, @samp{-nc}, @samp{-r}, or
@samp{-p}, downloading the same file in the same directory will result
in the original copy of @var{file} being preserved and the second copy
being named @samp{@var{file}.1}. If that file is downloaded yet
again, the third copy will be named @samp{@var{file}.2}, and so on.
(This is also the behavior with @samp{-nd}, even if @samp{-r} or
@samp{-p} are in effect.) When @samp{-nc} is specified, this behavior
is suppressed, and Wget will refuse to download newer copies of
@samp{@var{file}}. Therefore, ``@code{no-clobber}'' is actually a
misnomer in this mode---it's not clobbering that's prevented (as the
numeric suffixes were already preventing clobbering), but rather the
multiple version saving that's prevented.
When running Wget with @samp{-r} or @samp{-p}, but without @samp{-N}
or @samp{-nc}, re-downloading a file will result in the new copy
simply overwriting the old. Adding @samp{-nc} will prevent this
behavior, instead causing the original version to be preserved and any
newer copies on the server to be ignored.
When running Wget with @samp{-r} or @samp{-p}, but without @samp{-N},
@samp{-nd}, or @samp{-nc}, re-downloading a file will result in the
new copy simply overwriting the old. Adding @samp{-nc} will prevent
this behavior, instead causing the original version to be preserved
and any newer copies on the server to be ignored.
When running Wget with @samp{-N}, with or without @samp{-r} or
@samp{-p}, the decision as to whether or not to download a newer copy