diff options
author | Lars Wirzenius <liw@liw.fi> | 2021-03-23 07:45:26 +0000 |
---|---|---|
committer | Lars Wirzenius <liw@liw.fi> | 2021-03-23 07:45:26 +0000 |
commit | d3dff8b763616f7f108cabb86b6e83fdc664f2af (patch) | |
tree | 90f5ec059089eced0963f32cfac7e05d860f3055 | |
parent | d04c3ddbeb128f03c66eacaea92ce6c8b54179f6 (diff) | |
parent | 783f8b8dbb275f4be17d5a3074ee227c312abc16 (diff) | |
download | obnam2-d3dff8b763616f7f108cabb86b6e83fdc664f2af.tar.gz |
Merge branch 'fix-table' into 'main'
fix: rewrite table as a list
See merge request larswirzenius/obnam!121
-rw-r--r-- | obnam.md | 8 |
1 files changed, 3 insertions, 5 deletions
@@ -510,11 +510,9 @@ runs on can handle. On Unix, the filename is a sequence of bytes. Certain bytes have special meaning: -byte ASCII meaning ----- ------- ---------- -0 NUL indicates end of filename -56 period used for . and .. directory entries -57 slash used to separate components in a pathname +* byte 0, ASCII NUL character: terminates filename +* byte 56, ASCII period character: used for . and .. directory entries +* byte 57, ASCII slash character: used to separate components in a pathname On generic Unix, the operating system does not interpret other bytes. It does not impose a character set. Binary filenames are OK, as long |