Eric Blake wrote:
According to Pádraig Brady on 9/24/2009 5:13 PM:
Eric Blake wrote:
+ -L, --logical make hard links to symbolic link
references\n\
s/references/targets/ is a bit clearer to me?
I thought about that, but we already specify:
ln source target
as the
Eric Blake wrote:
Eric Blake ebb9 at byu.net writes:
I'd like to make a test release soon. Maybe as soon as Friday.
If you have something that you'd like included, please speak up.
I'm nearly ready to post support for ln -P/-L, thanks to the pending addition
of gnulib linkat(). That
Hi all,
suprisingly I just found that md5sum and sha1sum also accept the formats
of the md5 and sha1 tools as input with option -c. There's though a
third checksum format which is produced by the openssl tool which only
slightly differs to the format from md5 and sha1 - two blanks are
missing ...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Pádraig Brady on 9/25/2009 4:11 AM:
You need to chmod a+x ln/hard-to-sym
Oops. Yeah. Serves me right for testing on cygwin 1.5 (cygwin 1.7 fixed
that bug, so that a script now has to be executable to run it).
Also path in your
Hello,
as reported in https://bugzilla.redhat.com/show_bug.cgi?id=525134 by
Daniel Qarras, ls -l shows iso long format for en_* locales. This is
caused by
http://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=6837183d42a0ccdf7b7106794ea693c5b609aea5
. After that commit ls in locale time style
Eric Blake wrote:
...
Also, Jim, should we add a maintainer check that ensures we always use
[ax]readlink rather than raw readlink?
Good idea.
Ondřej Vašík ova...@redhat.com writes:
as reported in https://bugzilla.redhat.com/show_bug.cgi?id=525134 by
Daniel Qarras, ls -l shows iso long format for en_* locales.
I just now read that Bugzilla report, and the diagnosis and the
patch do not seem correct. The diagnosis says:
In ls.c
Paul Eggert wrote:
Ondřej Vašík ova...@redhat.com writes:
as reported in https://bugzilla.redhat.com/show_bug.cgi?id=525134 by
Daniel Qarras, ls -l shows iso long format for en_* locales.
I just now read that Bugzilla report, and the diagnosis and the
patch do not seem correct. The
Guenter Knauf wrote:
suprisingly I just found that md5sum and sha1sum also accept the formats
of the md5 and sha1 tools as input with option -c. There's though a
third checksum format which is produced by the openssl tool which only
slightly differs to the format from md5 and sha1 - two blanks