]>
Commit | Line | Data |
---|---|---|
e2e86c2f PS |
1 | --- tar-1.14/src/list.c.orig 2004-05-10 13:49:09.000000000 +0200 |
2 | +++ tar-1.14/src/list.c 2004-09-08 18:48:34.473169312 +0200 | |
3 | @@ -138,6 +138,14 @@ | |
4 | ||
5 | if (!ignore_zeros_option) | |
6 | { | |
7 | + break; | |
8 | + | |
9 | + /* | |
10 | + * According to POSIX tar specs, this is wrong, but on the web | |
11 | + * there are some tar specs that can trigger this, and some tar | |
12 | + * implementations create tars according to that spec... | |
13 | + * | |
14 | + | |
15 | char buf[UINTMAX_STRSIZE_BOUND]; | |
16 | ||
17 | status = read_header (false); | |
18 | @@ -146,6 +154,7 @@ | |
19 | WARN ((0, 0, _("A lone zero block at %s"), | |
20 | STRINGIFY_BIGINT (current_block_ordinal (), buf))); | |
21 | break; | |
22 | + */ | |
23 | } | |
24 | status = prev_status; | |
25 | continue; |