<feed xmlns='http://www.w3.org/2005/Atom'>
<title>coreutils/tests/ls, branch v9.4</title>
<subtitle>Mirror of https://https.git.savannah.gnu.org/git/coreutils.git/
</subtitle>
<id>https://git.shady.money/coreutils/atom?h=v9.4</id>
<link rel='self' href='https://git.shady.money/coreutils/atom?h=v9.4'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/'/>
<updated>2023-08-28T21:06:43Z</updated>
<entry>
<title>maint: spelling fixes, including author names</title>
<updated>2023-08-28T21:06:43Z</updated>
<author>
<name>Paul Eggert</name>
<email>eggert@cs.ucla.edu</email>
</author>
<published>2023-08-28T19:42:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=2dddc87214503199a38beeb175cd42cbb43cdff1'/>
<id>urn:sha1:2dddc87214503199a38beeb175cd42cbb43cdff1</id>
<content type='text'>
Most of this just affects commentary and documentations.  The only
significant behavior change is translating author names via
proper_name_lite rather than proper_name_utf8, or not translating
them at all.  proper_name_lite is good enough for coreutils and
avoids the bloat that had coreutils not using Gnulib proper_name.
* bootstrap.conf (gnulib_modules): Use propername-lite instead
of propername.
(XGETTEXT_OPTIONS): Look for proper_name_lite instead of for
proper_name_utf8.
* cfg.mk (local-checks-to-skip): Remove
sc_proper_name_utf8_requires_ICONV, since we no longer use
proper_name_utf8.
(old_NEWS_hash): Update.
(sc_check-I18N-AUTHORS): Remove; no longer needed.
</content>
</entry>
<entry>
<title>tests: move tests to a directory per utility</title>
<updated>2023-06-19T12:12:37Z</updated>
<author>
<name>Sylvestre Ledru</name>
<email>sylvestre@debian.org</email>
</author>
<published>2023-06-11T09:55:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=15925d0e5b80467c354fe27cb1205d6b6e3da11d'/>
<id>urn:sha1:15925d0e5b80467c354fe27cb1205d6b6e3da11d</id>
<content type='text'>
* cfg.mk: Adjust syntax check exclusion paths.
* tests/local.mk: Adjust for renamed tests.
</content>
</entry>
<entry>
<title>ls: display command line symlinks that return ELOOP</title>
<updated>2023-06-07T18:59:40Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2023-06-07T12:42:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=bf574deec8e811db230566fb085028aa6958d0fd'/>
<id>urn:sha1:bf574deec8e811db230566fb085028aa6958d0fd</id>
<content type='text'>
* src/ls.c (gobble_file): Ensure we lstat() a symlink
specified on the command line, if we receive ELOOP from stat().
* tests/ls/symlink-loop.sh: Add a new test.
* tests/local.mk: Reference the new test.
* NEWS: Mention the bug fix.
Fixes https://bugs.gnu.org/63931
</content>
</entry>
<entry>
<title>tests: avoid false failure on systems without statx</title>
<updated>2023-03-19T23:44:51Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2023-03-19T23:35:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=445f502839b6b13d051612e989a02a36f8b9176e'/>
<id>urn:sha1:445f502839b6b13d051612e989a02a36f8b9176e</id>
<content type='text'>
* tests/ls/stat-free-symlinks.sh: Filter out syscalls that
return ENOSYS, as that was seen with statx() on Debian 10.13
on mips64, and resulted in overcounting of stat calls.
</content>
</entry>
<entry>
<title>ls: --color: honor separate sequences for extension cases</title>
<updated>2023-03-13T16:20:38Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2022-09-04T18:59:25Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=47988fad885e8129f9dc36f0ed4d63375de23603'/>
<id>urn:sha1:47988fad885e8129f9dc36f0ed4d63375de23603</id>
<content type='text'>
Following on from commit v8.29-45-g24053fbd8 which unconditionally
used case insensitive extension matching, support selective
case sensitive matching when there are separate extension cases
defined with different display sequences.

* src/dircolors.hin: Document how file name suffixes are matched.
Note this is displayed with `dircolors --print-database` which
the texi info recommends to use for details.
* src/ls.c (parse_ls_color): Postprocess the list to
mark entries for case sensitive matching,
and also adjust so that unmatchable entries are more quickly ignored.
(get_color_indicator): Use exact matching rather than
case insensitive matching if so marked.
* tests/ls/color-ext.sh: Add test cases.
* NEWS: Mention the change in behavior.
Addresses https://bugs.gnu.org/33123
</content>
</entry>
<entry>
<title>maint: update all copyright year number ranges</title>
<updated>2023-01-01T14:50:15Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2023-01-01T14:50:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=01755d36e7389aef48f712193976205e7381115b'/>
<id>urn:sha1:01755d36e7389aef48f712193976205e7381115b</id>
<content type='text'>
Update to latest gnulib with new copyright year.
Run "make update-copyright" and then...

* tests/init.sh: Sync with gnulib to pick up copyright year.
* bootstrap: Manually update copyright year,
until we fully sync with gnulib at a later stage.
* tests/sample-test: Adjust to use the single most recent year.
</content>
</entry>
<entry>
<title>maint: avoid new grep -q syntax-check failures</title>
<updated>2022-11-15T14:02:10Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2022-11-15T13:27:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=e3bb9754485bf8e9c602565be223039d3a20c283'/>
<id>urn:sha1:e3bb9754485bf8e9c602565be223039d3a20c283</id>
<content type='text'>
* cfg.mk: Exclude NEWS from the check.
* init.cfg: s/grep -q/grep &gt;/dev/null/.
* tests/ls/hyperlink.sh: Likewise.
* tests/ls/symlink-quote.sh: Likewise.
</content>
</entry>
<entry>
<title>maint: update all copyright year number ranges</title>
<updated>2022-01-02T16:15:55Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2022-01-02T15:42:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=3067a9293af07ba2cf1ababe6b4482196717f806'/>
<id>urn:sha1:3067a9293af07ba2cf1ababe6b4482196717f806</id>
<content type='text'>
Run "make update-copyright" and then...

* gnulib: Update to latest with copyright year adjusted.
* tests/init.sh: Sync with gnulib to pick up copyright year.
* bootstrap: Likewise.
* tests/sample-test: Adjust to use the single most recent year.
</content>
</entry>
<entry>
<title>doc: colorize -&gt; color</title>
<updated>2021-12-24T17:49:21Z</updated>
<author>
<name>Paul Eggert</name>
<email>eggert@cs.ucla.edu</email>
</author>
<published>2021-12-24T17:47:18Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=d5ae6d812089053e473ab8ba320dfe6fd95f6b29'/>
<id>urn:sha1:d5ae6d812089053e473ab8ba320dfe6fd95f6b29</id>
<content type='text'>
Living so close to Hollywood I know that "colorize"
means adding color to something that was already monochrome,
whereas "color" means to give color to something.
Coreutils apps color text instead of colorizing it.
</content>
</entry>
<entry>
<title>tests: port removed-directory test to FreeBSD</title>
<updated>2021-09-16T23:18:03Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2021-09-16T23:17:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=5134612fa78012d8a8efeca181d1a9355d1fc67f'/>
<id>urn:sha1:5134612fa78012d8a8efeca181d1a9355d1fc67f</id>
<content type='text'>
* tests/ls/removed-directory.sh: On FreeBSD 9.1 at least,
one gets ENOENT when trying to traverse the current removed dir
with ../, so instead reference the parent dir directly.
</content>
</entry>
</feed>
