<feed xmlns='http://www.w3.org/2005/Atom'>
<title>coreutils, branch v8.6</title>
<subtitle>Mirror of https://https.git.savannah.gnu.org/git/coreutils.git/
</subtitle>
<id>https://git.shady.money/coreutils/atom?h=v8.6</id>
<link rel='self' href='https://git.shady.money/coreutils/atom?h=v8.6'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/'/>
<updated>2010-10-15T14:50:15Z</updated>
<entry>
<title>version 8.6</title>
<updated>2010-10-15T14:50:15Z</updated>
<author>
<name>Jim Meyering</name>
<email>meyering@redhat.com</email>
</author>
<published>2010-10-15T14:50:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=7612e5c5c6dcf41a04f53f52a35bbf6eb2c90b1b'/>
<id>urn:sha1:7612e5c5c6dcf41a04f53f52a35bbf6eb2c90b1b</id>
<content type='text'>
* NEWS: Record release date.
</content>
</entry>
<entry>
<title>build: update gnulib for vasnprintf fix</title>
<updated>2010-10-15T05:49:54Z</updated>
<author>
<name>Jim Meyering</name>
<email>meyering@redhat.com</email>
</author>
<published>2010-10-15T05:49:54Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=ff8d38e1003d3d7c61ac1cad57e6c75b2183ca53'/>
<id>urn:sha1:ff8d38e1003d3d7c61ac1cad57e6c75b2183ca53</id>
<content type='text'>
</content>
</entry>
<entry>
<title>bug#7213: [PATCH] sort: fix buffer overrun on 32-bit hosts when warning re obsolete keys</title>
<updated>2010-10-14T09:39:14Z</updated>
<author>
<name>Paul Eggert</name>
<email>eggert@cs.ucla.edu</email>
</author>
<published>2010-10-14T07:12:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=6b9ab1831f7b05883ed1797a5c71cf5c594b6124'/>
<id>urn:sha1:6b9ab1831f7b05883ed1797a5c71cf5c594b6124</id>
<content type='text'>
* src/sort.c (key_warnings): Local buffer should be of size
INT_BUFSIZE_BOUND (uintmax_t), not INT_BUFSIZE_BOUND (sword).
This bug was discovered by running 'make check' on a 32-bit
Solaris 8 sparc host, using Sun cc.  I saw several other instances
of invoking umaxtostr on a buffer declared to be of size
INT_BUFSIZE_BOUND (VAR), and these instances should at some point
be replaced by INT_BUFSIZE_BOUND (uintmax_t) too, as that's a
less error-prone style.
</content>
</entry>
<entry>
<title>tests: work around portability and clock-skew problems</title>
<updated>2010-10-14T07:23:51Z</updated>
<author>
<name>Paul Eggert</name>
<email>eggert@cs.ucla.edu</email>
</author>
<published>2010-10-14T06:39:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=7324fba6754b840a5d1fb6ec0f4ee3efb9db5ff4'/>
<id>urn:sha1:7324fba6754b840a5d1fb6ec0f4ee3efb9db5ff4</id>
<content type='text'>
* tests/misc/ls-misc (push_ls_colors): Don't assume LS_COLORS
is set.  This part of the fix is by Jim Meyering.
(sl-dangle2, sl-dangle3, sl-dangle4, sl-dangle5): Don't assume
that newly-created files will have time stamps in the past.  They
might not, due to clock skew, if the file systems are remote.
http://thread.gmane.org/gmane.comp.gnu.coreutils.bugs/21322/focus=21346
</content>
</entry>
<entry>
<title>install: avoid warning with Solaris 10 cc</title>
<updated>2010-10-14T05:41:21Z</updated>
<author>
<name>Paul Eggert</name>
<email>eggert@cs.ucla.edu</email>
</author>
<published>2010-10-14T03:44:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=c586bff1c0d36fc7b57c35fe7e5e8fbd00f83342'/>
<id>urn:sha1:c586bff1c0d36fc7b57c35fe7e5e8fbd00f83342</id>
<content type='text'>
* src/install.c (extra_mode): Don't assign ~S_IRWXUGO &amp; ~S_IFMT
to a mode_t variable, as the number might be too big to fit.
Solaris 10 cc warns about this, and the C standard says it
has undefined behavior.
</content>
</entry>
<entry>
<title>mbsalign: avoid warning with Solaris 10 cc</title>
<updated>2010-10-14T05:41:17Z</updated>
<author>
<name>Paul Eggert</name>
<email>eggert@cs.ucla.edu</email>
</author>
<published>2010-10-14T03:39:28Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=4015f93d3052b6b11ed5dbcdc032be324a084f07'/>
<id>urn:sha1:4015f93d3052b6b11ed5dbcdc032be324a084f07</id>
<content type='text'>
* gl/lib/mbsalign.c: Include &lt;stdint.h&gt; for SIZE_MAX.
Use SIZE_MAX rather than (size_t) -1, to avoid warning for
"size_t x = -1" on Solaris 10 cc.
* gl/modules/mbsalign (Depends-on): Add stdint.
</content>
</entry>
<entry>
<title>sort: fix unportable cast of unsigned char * -&gt; char *</title>
<updated>2010-10-14T05:41:13Z</updated>
<author>
<name>Paul Eggert</name>
<email>eggert@cs.ucla.edu</email>
</author>
<published>2010-10-14T03:35:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=34ef0a01f0e1d620dac17d35832449b6880641b0'/>
<id>urn:sha1:34ef0a01f0e1d620dac17d35832449b6880641b0</id>
<content type='text'>
* src/sort.c (fold_toupper): Change this back from char to
unsigned char, fixing a portability issue introduced in commit
59e2e55d0f154a388adc9bac37d2b45f2ba971f8 dated February 26, as the
C Standard doesn't let you convert from unsigned char * to char *
without a cast, and the (in theory more portable) style here is to
convert char values, not pointer values.
(getmonth): Convert char to unsigned char when needed for
comparison.
</content>
</entry>
<entry>
<title>build: prepare to enable -Werror also for gnulib-tests/</title>
<updated>2010-10-13T09:20:18Z</updated>
<author>
<name>Jim Meyering</name>
<email>meyering@redhat.com</email>
</author>
<published>2010-10-13T09:20:18Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=71a3fd73a1fa005ee4ac969e57b43f90237656b9'/>
<id>urn:sha1:71a3fd73a1fa005ee4ac969e57b43f90237656b9</id>
<content type='text'>
* configure.ac (GNULIB_WARN_CFLAGS): Define new variable, for use
in gnulib-tests.
* gnulib-tests/Makefile.am: Disable specific -W___ options,
but only for a few specific offending tests:
(test_xvasprintf_CFLAGS): Define.
(test_lock_CFLAGS, test_tls_CFLAGS): Define.
</content>
</entry>
<entry>
<title>tests: fix rand-isaac test</title>
<updated>2010-10-13T07:03:41Z</updated>
<author>
<name>Paul Eggert</name>
<email>eggert@cs.ucla.edu</email>
</author>
<published>2010-10-13T07:03:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=9300fffcb54006bf471d96d70cf98081152c6fb1'/>
<id>urn:sha1:9300fffcb54006bf471d96d70cf98081152c6fb1</id>
<content type='text'>
* gl/tests/test-rand-isaac.c (main): Fix swapped arguments to strtol.
</content>
</entry>
<entry>
<title>tail: fix checking of currently unavailable directories</title>
<updated>2010-10-12T10:41:17Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2010-10-12T00:39:58Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=61b77891c2d9af299063850a0c4d1d721340cfff'/>
<id>urn:sha1:61b77891c2d9af299063850a0c4d1d721340cfff</id>
<content type='text'>
* src/tail.c (tail_forever_inotify): Handle the case where
tail --follow=name with inotify, is not able to add a watch on
a specified directory.  This may happen due to inotify resource
limits or if the directory is currently missing or inaccessible.
In all these cases, revert to polling which will try to reopen
the file later.  Note inotify returns ENOSPC when it runs out
of resources, and instead we report a particular error message,
lest users think one of their file systems is full.
(main): Document another caveat with using inotify, where we
currently don't recheck directories recreated after the
initial watch is setup.
* tests/tail-2/F-vs-rename: Fix the endless loop triggered by
the above issue.
* tests/tail-2/inotify-hash-abuse: Likewise.
* tests/tail-2/wait: Don't fail in the resource exhaustion case.
* tests/tail-2/F-vs-missing: A new test for this failure mode
which was until now just triggered on older buggy linux kernels
which returned ENOSPC constantly from inotify_add_watch().
* NEWS: Mention the fix.
</content>
</entry>
</feed>
