<feed xmlns='http://www.w3.org/2005/Atom'>
<title>coreutils/src, branch v8.5</title>
<subtitle>Mirror of https://https.git.savannah.gnu.org/git/coreutils.git/
</subtitle>
<id>https://git.shady.money/coreutils/atom?h=v8.5</id>
<link rel='self' href='https://git.shady.money/coreutils/atom?h=v8.5'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/'/>
<updated>2010-04-23T13:44:19Z</updated>
<entry>
<title>tests: fix exit status of signal handlers in shell scripts</title>
<updated>2010-04-23T13:44:19Z</updated>
<author>
<name>Dmitry V. Levin</name>
<email>ldv@altlinux.org</email>
</author>
<published>2010-01-30T16:02:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=c0a121c9bccc6175dc3cdb705e2ec8cb2be9f71c'/>
<id>urn:sha1:c0a121c9bccc6175dc3cdb705e2ec8cb2be9f71c</id>
<content type='text'>
The value of `$?' on entrance to signal handlers in shell scripts
cannot be relied upon, so set the exit code explicitly.

* cfg.mk (sc_always_defined_macros, sc_system_h_headers): Set
the exit code in signal handler explicitly to 128 + SIG&lt;SIGNAL&gt;.
* src/Makefile.am (sc_tight_scope): Likewise.
* tests/test-lib.sh: Likewise.
</content>
</entry>
<entry>
<title>base64: always treat input in binary mode</title>
<updated>2010-04-22T14:42:54Z</updated>
<author>
<name>Eric Blake</name>
<email>eblake@redhat.com</email>
</author>
<published>2010-04-21T14:17:59Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=c9e4ea6ee2007462554568f156838b0fb6d55c9a'/>
<id>urn:sha1:c9e4ea6ee2007462554568f156838b0fb6d55c9a</id>
<content type='text'>
Necessary for cygwin.  Technically, this patch is not correct,
in that it clobbers O_APPEND, but it is no different than any
other use of xfreopen to force binary mode, so all such uses
should be fixed at once in a later patch.

* src/base64.c (main): Open input in binary mode.
* THANKS: Update.
Reported by Yutaka Amanai.
</content>
</entry>
<entry>
<title>sort: fix parsing of end field in obsolescent key formats</title>
<updated>2010-04-20T21:37:18Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2010-04-20T15:25:55Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=8fc12909f649fbe75eb84c48ace554ae3e4e6c06'/>
<id>urn:sha1:8fc12909f649fbe75eb84c48ace554ae3e4e6c06</id>
<content type='text'>
This regression was introduced in commit 224a69b5, 2009-02-24,
"sort: Fix two bugs with determining the end of field".
The specific regression being that we include 1 field too many when
an end field is specified using obsolescent key syntax (+POS -POS).

* src/sort.c (struct keyfield): Clarify the description of the eword
member, as suggested by Alan Curry.
(main): When processing obsolescent format key specifications,
normalize eword to a zero based count when no specific end char is given
for an end field. This matches what's done when keys are specified with -k.
* tests/misc/sort: Add a few more tests for the obsolescent key formats,
with test 07i being the particular failure addressed by this change.
* THANKS: Add Alan Curry who precisely identified the issue.
* NEWS: Mention the fix.
Reported by Santiago Rodríguez
</content>
</entry>
<entry>
<title>cp: preserve "capabilities" when also preserving file ownership</title>
<updated>2010-04-16T22:02:02Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2010-04-16T07:39:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=1777d0dfe34dc4d8c148a34a96eb92c6036ff7bd'/>
<id>urn:sha1:1777d0dfe34dc4d8c148a34a96eb92c6036ff7bd</id>
<content type='text'>
* src/copy.c (copy_reg): Copy xattrs _after_ setting file ownership
so that capabilities are not cleared when setting ownership.
* tests/cp/capability: A new root test.
* tests/Makefile.am (root_tests): Reference the new test.
* NEWS: Mention the fix.
</content>
</entry>
<entry>
<title>maint: fix build on platforms that replace strsignal</title>
<updated>2010-04-15T23:55:43Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2010-04-15T16:34:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=62dd4b63c5dc8c5ea37328f042c4ce4eaf41de9d'/>
<id>urn:sha1:62dd4b63c5dc8c5ea37328f042c4ce4eaf41de9d</id>
<content type='text'>
* src/Makefile.am (kill_LDADD): Add $(LIBTHREAD) so that
we link with the appropriate libraries to provide Thread Local Storage
on platforms that replace strsignal (like AIX for example).

Tested-by: Daniel Richard G. &lt;danielg@teragram.com&gt;
</content>
</entry>
<entry>
<title>cp: treat selinux warnings consistently</title>
<updated>2010-04-13T12:09:50Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2010-04-13T11:49:05Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=584e38d8b3199924ce24f9fa075d27d0d82a2a8b'/>
<id>urn:sha1:584e38d8b3199924ce24f9fa075d27d0d82a2a8b</id>
<content type='text'>
* src/copy.c (copy_reg): Suppress SELinux ENOTSUP warnings consistently
between the destination being present or not.  Previously we did
not suppress ENOTSUP messages when the destination was present.
(copy_internal): Use the same ENOTSUP supression method as
copy_reg() even though the issue was not seen in this case.
* tests/cp/cp-a-selinux: Add a test case for the issue and
group the other test cases in the file more coherently.
* tests/cp/cp-mv-enotsup-xattr: Do the same check for xattr
warnings, even though they did not have the issue.
</content>
</entry>
<entry>
<title>doc: clarify when cp and mv output xattr warnings</title>
<updated>2010-04-12T09:06:11Z</updated>
<author>
<name>Pádraig Brady</name>
<email>P@draigBrady.com</email>
</author>
<published>2010-04-12T07:46:37Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=c420cfef77b9173a754806dc49deacabb436044f'/>
<id>urn:sha1:c420cfef77b9173a754806dc49deacabb436044f</id>
<content type='text'>
The 2010-03-26 commit, 4c38625e, "doc: fix info on cp --preserve..."
was not entirely correct as cp --preserve=all does produce some
xattr warnings.

* src/copy.h: Update and clarify the comments for reduce_diagnostics
and require_preserve_{xattr,context}.
* doc/coreutils.texi (cp invocation): Update the -a and
--preserve=xattr,context options to say when and which
xattr warnings are output.
(mv invocation): Mention that some warnings are output
when preserving xattrs.
</content>
</entry>
<entry>
<title>dircolors: add rxvt-256color and rxvt-unicode256</title>
<updated>2010-04-09T14:28:46Z</updated>
<author>
<name>Mike Frysinger</name>
<email>vapier@gentoo.org</email>
</author>
<published>2010-04-09T06:16:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=ac6feeb9f226247a53ab5b6c3aa24e40caabdc40'/>
<id>urn:sha1:ac6feeb9f226247a53ab5b6c3aa24e40caabdc40</id>
<content type='text'>
* src/dircolors.hin: Add them.
</content>
</entry>
<entry>
<title>maint: ftruncate is always available, even without gnulib</title>
<updated>2010-04-09T08:50:43Z</updated>
<author>
<name>Jim Meyering</name>
<email>meyering@redhat.com</email>
</author>
<published>2010-04-09T08:49:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=ef5758c3282b3325340d8b601deed5ab5e7ade64'/>
<id>urn:sha1:ef5758c3282b3325340d8b601deed5ab5e7ade64</id>
<content type='text'>
Now that even MinGW provides ftruncate, we know that all
reasonable portability targets provide this function.
Remove the workaround code.  We nearly removed the gnulib
module three years ago:
  http://thread.gmane.org/gmane.comp.lib.gnulib.bugs/9203
and it is now officially "obsolete".
* bootstrap.conf (gnulib_modules): Remove ftruncate.
* src/copy.c (copy_reg): Remove use of HAVE_FTRUNCATE and its
no-longer-used workaround code.
* src/truncate.c: Remove a comment about handling missing ftruncate.
</content>
</entry>
<entry>
<title>doc: make wc --help say how it defines a 'word'</title>
<updated>2010-04-08T21:53:12Z</updated>
<author>
<name>James Youngman</name>
<email>jay@gnu.org</email>
</author>
<published>2010-04-08T09:58:52Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/coreutils/commit/?id=0a9302e7f796bc59a17f85fed00f0350c8330e12'/>
<id>urn:sha1:0a9302e7f796bc59a17f85fed00f0350c8330e12</id>
<content type='text'>
* src/wc.c (usage): Add wc's definition of "word".
</content>
</entry>
</feed>
