There have been *many* changes in gnulib since the previous snapshot,
and the changes in coreutils are non-negligible, so please give
this a try. I'd like to make the beta release on Monday.
I'll probably call it coreutils-8.0.
coreutils snapshot:
http://meyering.net/cu/coreutils-ss.tar.gz
Slosh/slash problem in DU 5.3.0 Windows build :
Specifying du c:\ results in lots of error messages like :
...\DU.EXE: cannot access 'c:\\/WINDOWS' : Permission denied
...\DU.EXE: cannot access 'c:\\/My Documents' : Permission denied
...\DU.EXE: cannot access 'c:\\/COMMAND.COM' : Permission
I was moving some files with mv from a hard drive to a flash drive. The
flash drive is very slow. The mv command finished and the original files
were gone but I realized the operating system still had a gigabyte or so of
data in RAM which was in the process of being written to the flash disk.
Hello!
This particular default version of tail cannot handle the argument,
+line-number.
This shortcoming does not permit portability. The work-around is to do more
math than is necessary.
Examples:
Old version of tail.
[mbarn...@corp bin]$ tail --version
tail (coreutils) 5.2.1
Written
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to barnettm...@comcast.net on 10/3/2009 2:59 AM:
Hello!
This particular default version of tail cannot handle the argument,
+line-number.
Not a bug. This behavior is required by newer versions of POSIX.
Use 'tail -n +line-number'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to da Silva, Joe on 10/1/2009 10:18 PM:
Slosh/slash problem in DU 5.3.0 Windows build :
5.3.0 is quite old; the latest stable version is 6.7, and may have
portability fixes that have improved the behavior of du on Windows.
However, we
Since the patch is really small I would like to ask you for a review
without urging me to go through all the git stuff;
It's really not that hard.
Have you looked at the instructions here?
http://git.sv.gnu.org/cgit/coreutils.git/plain/HACKING
if you accept the
simple patch then I will
Hi Jim,
Jim Meyering schrieb:
Would you like to write the patch (including NEWS and
a small doc update), following these guidelines?
http://git.sv.gnu.org/cgit/coreutils.git/plain/HACKING
I've just tested a bit, and it seems that its enough to hack around the
first place where the blank can
Jim,
thanks for the very quick review.
Jim Meyering schrieb:
Guenter Knauf wrote:
- size_t i;
+ size_t i = 0;
bool escaped_filename = false;
size_t algo_name_len;
- i = 0;
while (ISWHITE (s[i]))
++i;
Instead, please move the declaration down.
hmm, not sure what you
Guenter Knauf wrote:
Jim,
thanks for the very quick review.
Jim Meyering schrieb:
Guenter Knauf wrote:
- size_t i;
+ size_t i = 0;
bool escaped_filename = false;
size_t algo_name_len;
- i = 0;
while (ISWHITE (s[i]))
++i;
Instead, please move the declaration down.
Hi Jim,
Jim Meyering schrieb:
This is what I meant:
...
- i = 0;
+ size_t i = 0;
while (ISWHITE (s[i]))
++i;
ok, added.
make check runs most tests.
Use this
make check -C tests TESTS=misc/md5sum VERBOSE=yes
to run just the one you changed.
thanks, tests passed:
PASS:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 10/3/2009 2:30 AM:
There have been *many* changes in gnulib since the previous snapshot,
and the changes in coreutils are non-negligible, so please give
this a try. I'd like to make the beta release on Monday.
I'll
Jim Meyering wrote:
Maybe you want a new option to enable this behavior when
does not do an atomic rename, but it will never be the
efault, because it would cause a huge performance hit
when copying many files between devices.
True, it's the classic reliability vs performance tradeoff,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
$ echo abc | tail -c +1
tail: cannot open `+1' for reading: No such file or directory
$ echo abc | tail -c+1
abc
$ tail --version | head -n1
tail (GNU coreutils) 7.6
Shouldn't -c behave the same, whether or not there is a space before the
count
14 matches
Mail list logo
