Re: du bug

2009-03-21 Thread Jim Meyering
Eric Blake wrote: > [please keep replies on the list, so that others may chime in] > > According to Robin McAdam on 3/21/2009 7:26 PM: >>> That warning was in place to warn of a future change in behavior. The >>> change has now been completed, and you will not get that warning in >>> coreutils 7.1

Re: du bug

2009-03-21 Thread Micah Cowan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric Blake wrote: > [please keep replies on the list, so that others may chime in] > > According to Robin McAdam on 3/21/2009 7:26 PM: >>> That warning was in place to warn of a future change in behavior. The >>> change has now been completed, and yo

Re: du bug

2009-03-21 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [please keep replies on the list, so that others may chime in] According to Robin McAdam on 3/21/2009 7:26 PM: >> That warning was in place to warn of a future change in behavior. The >> change has now been completed, and you will not get that warnin

Re: [PATCH] in place option for unexpand

2009-03-21 Thread Pádraig Brady
Sami Kerola wrote: > Good weekend, > > If you consider in-line option is useful for unexpand I could wrote > another patch for expand command which will do the same thing. Thanks for this. I'm wondering about usefulness to other coreutils. Perhaps fmt,fold,nl,tac,tr would also benefit in addition

Re: du bug

2009-03-21 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Robin McAdam on 3/21/2009 6:35 PM: > > Appears to be a bug with: > du -sH * Documents\ and\ Settings/ I'm not sure I spot what you think is the bug. Everything in your trace looked like expected behavior. I'm guessing that maybe you we

du bug

2009-03-21 Thread Robin McAdam
Appears to be a bug with: du -sH * Documents\ and\ Settings/ I'm a layman. discovered by mistyping. xpu...@amdxp2100:/mnt/160G-1$ xpu...@amdxp2100:/mnt/160G-1$ xpu...@amdxp2100:/mnt/160G-1$ du --v du (GNU coreutils) 6.10 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL

Re: coreutils 7.1.49-ebb9 FTB sparc/Solaris, AIX

2009-03-21 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 3/20/2009 6:30 AM: >> $ find /usr/include | xargs grep sig_atomic_t >> /usr/include/sys/signal.h:typedef volatile int sig_atomic_t; > > Therefore, 'volatile sig_atomic_t' is not a bug, even if sig_atomic_t > already included

[PATCH] in place option for unexpand

2009-03-21 Thread Sami Kerola
Good weekend, If you consider in-line option is useful for unexpand I could wrote another patch for expand command which will do the same thing. -- Sami Kerola http://www.iki.fi/kerolasa/ From ef6192da066dcf3c65bc9a672ecf78c30894ac95 Mon Sep 17 00:00:00 2001 From: Sami Kerola Date: Sat, 21

Re: new snapshot available: coreutils-7.1.71-e0149

2009-03-21 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jim Meyering on 3/21/2009 11:20 AM: > Changes since 7.1.63-8e6a6: > * gnulib: Update submodule to latest. > > There have been a few portability fixes via gnulib, too. This is a fun trick to list those changes: $ git submodule sum

new snapshot available: coreutils-7.1.71-e0149

2009-03-21 Thread Jim Meyering
There have been a few portability and test-related fixes since last snapshot. The only pending bug-fix is the one for ls -v, which should come via gnulib's strverscmp module. coreutils snapshot: http://meyering.net/cu/coreutils-ss.tar.gz 9.3 MB http://meyering.net/cu/coreutils-ss.tar.xz

make syntax-check clean-up

2009-03-21 Thread Jim Meyering
Due to the presence of a huge residual hierarchy in my build tree, parts of "make syntax-check" were taking way too long -- they were running "find" on the working directory rather than using VC_LIST_EXCEPT. Fixing that in two rules, I spotted a recommendation to use the obsolescent @PATH_SEPARATOR