[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ChangeLog encoding; testsuite file/s
From: |
Adam Tuja |
Subject: |
Re: ChangeLog encoding; testsuite file/s |
Date: |
Mon, 24 Jan 2022 23:57:51 +0100 |
Sorry for delay.
Reason I brought it is, there is (almost) always way to do something better.And also observation, that `test.txt/.lz' is "doubled" `COPYING' from source directory. Therefore it can be generated. Same with `test_em.lz', something along those lines:
```
#!/bin/sh
...
printf "" > 0
cat ../README > A
cat ../COPYING > B
cat A B | lzip -c > testab1.lz
Test2="0 A 0 0 B 0"
for f in $Test2; do
lzip -c $f >> testab2.lz
done
```
The last, as you mentioned gzip - all tests there are generated, and size is due to the sources, not tests.
Regards
Adam
- adjust texinfo category for lzip, Alfred M. Szmidt, 2022/01/10
- Re: adjust texinfo category for lzip, Antonio Diaz Diaz, 2022/01/10
- ChangeLog encoding; testsuite file/s, Adam Tuja, 2022/01/12
- Re: ChangeLog encoding; testsuite file/s, Adam Tuja, 2022/01/17
- Re: ChangeLog encoding; testsuite file/s, Antonio Diaz Diaz, 2022/01/17
- Re: ChangeLog encoding; testsuite file/s,
Adam Tuja <=
- Re: ChangeLog encoding; testsuite file/s, Antonio Diaz Diaz, 2022/01/25
- Re: ChangeLog encoding; testsuite file/s, Adam Tuja, 2022/01/26
- Re: ChangeLog encoding; testsuite file/s, Antonio Diaz Diaz, 2022/01/26