diff options
| author | Jim Meyering <meyering@redhat.com> | 2007-10-08 10:34:04 +0200 |
|---|---|---|
| committer | Jim Meyering <meyering@redhat.com> | 2007-10-08 10:47:40 +0200 |
| commit | e6f4b28275316895ad8808a9d0abcc468df8780b (patch) | |
| tree | 7bd4c3e13a773b3dfd074077f22ec75bbe1c7a22 /ChangeLog | |
| parent | 689186b88ccf025664ca24ac8efa68699f12d85d (diff) | |
| download | coreutils-e6f4b28275316895ad8808a9d0abcc468df8780b.tar.xz | |
When forming a truncated name, use the "[...]" prefix even for
an extremely long name in the current directory.
* src/remove.c (full_filename_): Rename a local variable.
Use two separate "truncated" variables, in case the second
call to right_justify does not indicate any truncation -- which
would happen only if the single component FILENAME were longer
than 511 bytes and DIR_NAME were empty.
Diffstat (limited to 'ChangeLog')
| -rw-r--r-- | ChangeLog | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -1,5 +1,13 @@ 2007-10-08 Jim Meyering <meyering@redhat.com> + When forming a truncated name, use the "[...]" prefix even for + an extremely long name in the current directory + * src/remove.c (full_filename_): Rename a local variable. + Use two separate "truncated" variables, in case the second + call to right_justify does not indicate any truncation -- which + would happen only if the single component FILENAME were longer + than 511 bytes and DIR_NAME were empty. + rm could malfunction under unusual circumstances: When operating on a relative name longer than 511 bytes, and (when either processing a directory that is neither writable |