On 5/11/24 23:54, Karl-Heinz Oliv via GNU coreutils General Discussion wrote:
> Hi,
>
> I am having problems with the evaluation/output order of 'du (GNU
> coreutils) 8.32'.First tests below show that glob expansion of '*' and
> language specific sorting work as expected. 'du' intrinsic
On 4/9/24 2:21 PM, Pádraig Brady wrote:
Thanks for looking at this.
From the Fedora side, they dropped a Fedora specific patch for Fedora 38.
https://bugzilla.redhat.com/show_bug.cgi?id=548834
https://bugzilla.redhat.com/show_bug.cgi?id=2208048
FWIW: OpenSUSE still has that patch which was
On 4/9/24 10:20 PM, Carl Edquist wrote:
On Tue, 9 Apr 2024, Tony Freeman wrote:
I seem to recall that some years ago ls -l would show the number of hard
links to a file.
Yes with "ls -l" it's the first number you see (after the permissions string). Or you
can use "stat -c %h filename" to
On 3/23/24 14:57, Pádraig Brady wrote:
On 23/03/2024 10:18, Bernhard Voelker wrote:
On my openSUSE:Tumbleweed system, the info pages seem to have changed
the quoting style for the strftime for the conversion specifiers from
the good old '%a' or `%a' styles to ‘%a’.
$ info libc date
On 3/22/24 11:22, Karel Zak wrote:
> On Wed, Mar 20, 2024 at 11:53:05PM +0100, Bernhard Voelker wrote:>> On
userland OTOH, we have broader choice.
>> Karel did his choice in util-linux for exch(1), and coreutils could expose
>> the same functionality.
>>
>> Fo
On 3/23/24 02:44, Paul Eggert wrote:
I installed the attached patches to do the above. (Basically, the
problem was that my earlier patches were too ambitious; these patches
scale things back to avoid some optimizations so that mv --exchange is
more like ordinary mv.)
The first patch simplifies
On my openSUSE:Tumbleweed system, the info pages seem to have changed
the quoting style for the strftime for the conversion specifiers from
the good old '%a' or `%a' styles to ‘%a’.
$ info libc date calendar format | grep '^[^a-z%]*%.[^a-z%]*$' | od -tx1z |
sed 1q
000 20 20 20 20 20 e2
On 3/21/24 00:56, Paul Eggert wrote:
On 3/20/24 15:53, Bernhard Voelker wrote:
Yes, that's the expected behavior for this contrived case. Just as one
would get odd behavior if one did the same thing without --exchange.
There's another which is not consistent with/without --exchange:
$ src
On 3/20/24 21:56, Paul Eggert wrote:
On 3/20/24 12:43, Bernhard Voelker wrote:
This stems from the fact that although mv(1) is a userland frontend
for renameat(2), the user interface is different:
while renameat(2) deals exactly with 2 operands, mv(1) has always
been able to work on more
On 3/17/24 07:10, Paul Eggert wrote:
Although removing that "mv --swap" implementation was a win, I don't
think we can simply delegate this to util-linux's exch command.
I still have some headache adding this.
This stems from the fact that although mv(1) is a userland frontend
for
In [1], the point is raised why the following fails (as a non-privileged user):
> $ chmod a+x /usr/bin/ls
> chmod: changing permissions of '/usr/bin/ls': Operation not permitted
>
> However, /usr/bin/ls is already executable, there is no need to change
permissions,
> hence no need to report a
On 2/9/24 09:22, aotto wrote:
for my special case the "ln -s .." is even don't work with git
reading the report you mentioned [1], I suggest doing it the other way round:
create a symlink in the directory where you generate the output and let it point
to the directory in your git working tree.
[+coreutils ML]
On 2/8/24 17:43, aotto wrote:
> Hi, I write to you because of a suggestion from the "https://serverfault.com/;
Q side
you sent this to my personal email, so you're lucky this didn't land in spam.
Hence I'm hereby forwarding to the coreutils mailing list.
> subtract: add a "-m"
On 2/1/24 01:39, SNUGGS wrote:
Any reason there is a duplicate `C_FILE` in `ls.c`?
https://github.com/coreutils/coreutils/blame/master/src/ls.c#L184-L185
The list directly corresponds to the 'enum filetype' some lines above:
enum filetype
{
unknown,
fifo,
chardev,
tag 68866 notabug
close 68866
stop
On 2/1/24 04:09, Seungchul Lee wrote:
man page description has following line,
"If no option is specified, -P is assumed."
But in my machine, its default behavior seems -L without any option for pwd.
'man pwd' and 'env pwd --help' also tells:
NOTE: your
On 12/26/23 04:53, Kaz Kylheku wrote:
The feature is actually implementable. The cat program has a way of
determining that it has been passed all the names that may arise
from the expansion of *. (Modulo a minor sampling-related race
condition.) Namely, it can just call glob("*", ...) and
On 12/15/23 14:22, Pádraig Brady wrote:
On 31/10/2023 19:49, Pádraig Brady wrote:
On 31/10/2023 17:51, Ed Neville wrote:
Hi there,
Please could one of the maintainers take a look at this patch? Is it
ready for merge? It should be a straight forward change that brings the
same functionality
On 12/15/23 21:13, Michael Stone wrote:
On Fri, Dec 15, 2023 at 11:21:06AM -0800, Paul Eggert wrote:
Stlll, Pádraig gave a reasonable summary of why the change was made,
despite its incompatibility with previous behavior. (One thing I'd add
is that the FreeBSD behavior is inherently less
On 10/16/23 08:35, Dani Moncayo wrote:
On Mon, Oct 16, 2023 at 8:19 AM Dani Moncayo wrote:
Maybe someone could figure out a better way of specifying several
field-delimiters.
Perhaps a long option, like:
If (and only if) such a feature would be added, then it would make sense
to
[redirecting to the ML]
Hi Gerard,
please do not send to maintainers directly, but to the mailing list instead.
Besides this should be an open discussion in the public, chances are that such
messages land in the spam folder of all recipients.
On 10/3/23 10:42, Gerard T. wrote:
Hi folks,
On 9/25/23 08:12, Owen Chia wrote:
Dear GNU Coreutils Team,
I hope this email finds you well. I am writing to propose a feature request
regarding the 'rm' command in GNU Coreutils. Specifically, I would like to
suggest the removal of the '-f' short option, while retaining the '--force'
long
On 9/25/23 01:25, Dennis German wrote:
> I'd like to understand why you feel that
> " ability to view the source as-is, with no rendering applied"
> is important
Because that is how software development is done. It's all about
changes to some kind of text, be it either program source code or
On 9/23/23 18:35, Jeffrey Cliff wrote:
Test suite told me to send this report in so here we are.
environment : custom LFS (GNM)
coreutils: 9.4
gcc: (GCC) 13.2.0
> FAIL: tests/rm/ext3-perf
>
> [...]
>
> ++ date +%s
> + start=1698065263
> + mkdir d
> + cd d
> + xargs
On 9/24/23 14:37, Dennis German wrote:
After the years and fine tuning of basic HTML, why aren't the man pages
standardized to HTML format?
Perhaps some users don't frequently enough reference man pages as they
should and fewer use info , but (nearly) everyone uses a browser.
Sorry, I don't
On 8/15/23 17:19, Pádraig Brady wrote:
+1
thanks, pushed.
On 8/15/23 17:18, Pádraig Brady wrote:
+1
thanks, pushed.
Sorry, somehow my `git send-email` is broken currently, so I have to attach
even this trivial patch.
Have a nice day,
BernyFrom 0cb8332196d3c727f540de407228ecb910e12e25 Mon Sep 17 00:00:00 2001
From: Bernhard Voelker
Date: Tue, 15 Aug 2023 13:35:13 +0200
Subject: [PATCH] maint: fix typo
On 8/12/23 14:05, Sergey Ponomarev wrote:
For sure it would be good to add mention of the install into man cp "SEE
ALSO".
Good idea. Patch attached ... pushing soon.
Have a nice day,
BernyFrom d428096a6ade1acfc6537ab5f138ef1a3531a0fc Mon Sep 17 00:00:00 2001
From: Bernhard Voelker
On 7/15/23 00:35, Michael Partridge via GNU coreutils General Discussion wrote:
Could you add the following to the example to the man page:
```txt
Show the current date and time using a custom format
$ date "+%Y-%m-%d %H:%M"
```
IMO this is already explained:
date [OPTION]...
On 7/15/23 23:08, Pádraig Brady wrote:
The attached patch-set addresses two classes of issue:
1. Doubled error messages upon write errors
2. Continued processing upon write errors (the orig problem reported).
Nice work!
Patch 1:
> --- /dev/null
> +++ b/tests/misc/write-errors.sh
> @@ -0,0
On 7/1/23 14:12, Sergey Ponomarev wrote:
> To rename a file a user need to use mv command and specify the DEST dir:
>
> mv /some/very/long/path/file /some/very/long/path/
>
> This makes it not so easy to use when typing a command but also makes a
> script line longer.
Assuming you meant
[moving this from the openSUSE list to upstream coreutils]
Hi Padraig,
On 6/29/23 08:21, Thorsten Kukuk wrote:
On Thu, Jun 29, Bernhard Voelker wrote:
Hi Thorsten,
On 6/28/23 10:40, Thorsten Kukuk wrote:
On openSUSE Tumbleweed/MicroOS/... we introduced meanwhile wtmpdb, which
solves
tag 64326 notabug
close 64326
stop
On 6/28/23 19:33, Chris Elvidge wrote:
> On 28/06/2023 16:41, Arsen Arsenović via GNU coreutils Bug Reports wrote:
>> Hi,
>>
>> LitHack writes:
>>
>>> Basically what it doing is that it doesn't recognise (-) this as a file
>>> name part even when using (\-).
tag 63732 notabug
close 63732
stop
On 5/26/23 02:26, Greg Carter via GNU coreutils Bug Reports wrote:
Got this when executing `tail -f install/MYSYBASE.log` for an SAP ASE
message log (a text file) with a Docker container:
```
tail: unrecognized file system type 0x794c7630 for
On 5/9/23 20:57, Bruno Haible wrote:
Bernhard Voelker wrote:
I noticed the issue because the following "very-expensive" tests failed
(which succeeded with coreutils-9.3):
FAIL: tests/rm/ext3-perf
FAIL: tests/rm/many-dir-entries-vs-OOM
Did you notice these failures by cha
On 5/7/23 21:55, Pádraig Brady wrote:
+1
Pushed, thanks for the review.
Have a nice day,
Berny
t failed,
which was coreutils commit 941027eeb for the gnulib update, and the
went for and back and forth in the gnulib history.
The attached coreutils patch updates gnulib to latest to fix the bug.
Have a nice day,
BernyFrom 131f5c998d5eecfcaed46ea3b5ca2ac93b3737fa Mon Sep 17 00:00:00 2001
From:
On 4/7/23 11:39, Pádraig Brady wrote:
In that thread I did suggest a diagnostic would be appropriate here.
Thinking more about it I'm more convinced we should diagnose here
especially as we're changing long standing behavior of --no-clobber.
The attached outputs new "skipped" errors with
On 4/6/23 23:02, Arsen Arsenović wrote:
See discussion at https://debbugs.gnu.org/62572
oh, I've fallen quite behind with reading all threads, sorry.
Thanks for the pointer.
Have a nice day,
Berny
Hi,
I saw a discussion about 'cp -n A B' now exiting with 9.2 when B exists.
That seems to have changed with v9.1-133-g7a69df889.
I don't question that change, but shouldn't the tool output an error diagnostic
if it exits with an error?
$ cp -n A B; echo $?
1
It doesn't even give a hint
On 3/17/23 19:47, Pádraig Brady wrote:
Please apply.
Thanks, pushed.
Have a nice day,
Berny
On 3/17/23 13:16, Pádraig Brady wrote:
For backwards compat, do we need to use something like
the se_const wrapper we used to have?
https://github.com/coreutils/coreutils/commit/8e764584f
(eventually removed in):
https://github.com/coreutils/coreutils/commit/e53bb7ad0
As it's about the return
Since SELinux version 3.5, the return value of context_str(3) is
declared as const; see:
https://github.com/SELinuxProject/selinux/commit/dd98fa322766
Therefore, GCC complains (here with -Werror):
src/selinux.c: In function 'defaultcon':
src/selinux.c:152:16: error: assignment discards
tag 61530 notabug
close 61530
stop
On 2/15/23 14:28, Andreas Löw wrote:
Hello,
I want to check a single file for correct sha256. All the files of my
directory are included in a sha256 text file named allsha256.
The sha256sum always checks all files included in the allsha256
On 2/10/23 23:47, SCOTT FIELDS wrote:
> I'm looking to get the number of files in each directory under a given path
> But only the top level of each directory (don't include files/directories from
> subdirectories in each processed directory)
>
> Example from your statement:
>
> # du --inodes -d
On 2/11/23 11:03, Gunnar Lindholm wrote:
10 feb. 2023 kl. 23:09 skrev Bernhard Voelker :
On 2/3/23 20:58, Gunnar Lindholm wrote:
+With the @option{-b} and @option{-f} options one can use the exit status to
+verify the available space (in bytes or percentage) with a command like
+@samp{if df -b
On 2/3/23 08:12, Dan Jacobson wrote:
uniq INFO page says:
‘-u’
‘--unique’
Discard the last line that would be output for a repeated input
group. When used by itself, this option causes ‘uniq’ to print
unique lines, and nothing else.
This really needs some examples, to help
On 2/3/23 20:58, Gunnar Lindholm wrote:
> +With the @option{-b} and @option{-f} options one can use the exit status to
> +verify the available space (in bytes or percentage) with a command like
> +@samp{if df -b 64 /var/log ; then echo "That is big enough for
everyone"; fi}
Thanks for the
On 2/8/23 20:56, SCOTT FIELDS via GNU coreutils General Discussion wrote:
I'm wanting to get a per directory inode report.
The problem I have with "du -inodes" is that the inode report for a directory
includes all inodes for subdirectories.
But...if I use "-S" the subdirectory entry itself
On 1/3/23 13:04, Pádraig Brady wrote:
looks good.
thanks, pushed.
Have a nice day,
Berny
tag 60512 notabug
close 60512
stop
On 1/3/23 10:27, 闵续 wrote:
tail: unrecognized file system type 0x794c7630 for ‘douyin.search.api.log’.
please report this to bug-coreutils@gnu.org. reverting to polling
Thanks for the report.
That docker image seems to use a quite old coreutils version:
Newer grep(1) complains:
$ make sc_prohibit_test_minus_ao
/usr/bin/grep: warning: * at start of expression
prohibit_test_minus_ao
* cfg.mk (exclude_file_name_regexp--sc_prohibit_test_minus_ao): Fix
expression inroduced in v8.24-120-g3205bb178, and narrow down the file
pattern to the 'doc/'
Hi Padraig,
On 12/28/22 15:11, Pádraig Brady wrote:
* src/wc.c (wc): Use off_t rather than size_t
when calculating where to seek to, so that
we don't seek to a too low offset on systems
where size_t < off_t, which would result in
many read() calls to determine the file size.
*
On 12/19/22 09:30, dchme...@gmail.com wrote:
Lately I read about the expr command, which I'm arguing is programmed
wrong for only working right when you put spaces into expressions rather
than working for standard mathematical expressions, which don't use
spaces. Think back to your mathematics
tag 59461 notabug
close 59461
stop
On 11/21/22 10:21, 林兴隆 wrote:
OS: Rocky Linux release 9.0 (Blue Onyx)
kenel: 5.14.0-70.22.1.el9_0.x86_64
Docker: 20.10.21, build baeda1f
Docker-Compose: v2.11.2
I use docker compose to run a container activemq,The contents are as
follows,Error
tag 59304 notabug
close 59304
stop
On 11/16/22 05:44, Stuart Rothrock wrote:
tail -f /var/log/melog | while read a; do echo $(date) $(echo $a | sed -e
's/[{}",]//g' -e 's/[a-z]\+://g'); done 2>&1 | tee -a dock2.log
tail -f power-dock2.log
tail: unrecognized file system type 0x794c7630 for
Hi *,
after one of the recent gnulib updates, the 'bootstrap' script has diverged
from 'gnulib/build-aux/bootstrap'.
Gnulib has introduced autopull.sh and autogen.sh in commit 096abe49088.
Shouldn't we use that, too?
Have a nice day,
Berny
On 10/27/22 16:41, Pádraig Brady wrote:
Previously this was restricted to the C standard subset
which restricted most values <= 0x9F, as that simplifies the C lexer.
However printf(1) doesn't need this restriction.
Note also the bash builtin printf already supports all values <= 0x9F.
Nice
On 9/2/22 07:21, amar monsef wrote:
I installed Kali Linux (not a graphical install)
And windows doesn't open anymore ,I need to uninstall it and uninstall gnu
sorry, you've reached the GNU coreutils mailing list where we only discuss
about the upstream development of that package.
We don't
On 8/31/22 20:19, Pádraig Brady wrote:
[PATCH] stty: add an undocumented ---debug option for more info
+1 nice!
Have a nice day,
Berny
On 8/31/22 01:22, Pádraig Brady wrote:
Subject: [PATCH] stty: valid ispeed and ospeed arguments
_^
s/valid//
+1 otherwise, thanks.
Have a nice day,
Berny
On 8/18/22 20:19, Pádraig Brady wrote:
I would do an `ef2sck -f` on the unmounted file system if possible.
Could also be an unusual "Reserved blocks" percentage for the root user.
See `tune2fs -l $DEVICE`.
Have a nice day,
Berny
tag 56631 notabug
close 56631
stop
On 7/18/22 12:50, Alexey Kuznetsov wrote:
> Simple bash script:
>
> #!/bin/bashset -eexec 7<"$0"flock -n 7sleep 60
>
> Will prevent a second instance from being executed (exits instantly). But
> if the first instance got killed by 'killall test.sh', the second
tag 55837 notabug
close 55837
stop
On 6/8/22 02:28, Klaatu wrote:
According to the man page, `--tmpfile` is the long option for `-p`
However, I get different results when using one or the other.
The `-p` option results in success:
$ mktemp -p ~/Demo
/home/klaatu/Demo/tmp.6TWPxScyKK
$ mktemp
On 5/26/22 17:39, Pádraig Brady wrote:
> On 26/05/2022 15:14, Bernhard Voelker wrote:
>> * NEWS: s/x86-64/x86_64/
> That's consistent with all other uses.
Thanks, pushed.
Have a nice day,
Berny
* NEWS: s/x86-64/x86_64/
---
NEWS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index 16984003c..8c3eb9b25 100644
--- a/NEWS
+++ b/NEWS
@@ -8,7 +8,7 @@ GNU coreutils NEWS-*-
outline -*-
[bug introduced in coreutils-9.1]
On 5/9/22 15:42, Pádraig Brady wrote:
> Excellent review.
Thanks.
> Agreed on all points.
> Updated patch is attached.
+1
Have a nice day,
Berny
Hi Padraig,
On 5/8/22 14:44, Pádraig Brady wrote:
> I'll apply the attached later.
I found some nits - see below.
> From f83b1e7b1c6d2a2c0211cc1097dc165a1918d8f3 Mon Sep 17 00:00:00 2001
> From: Rasmus Villemoes
> Date: Wed, 27 Apr 2022 12:07:20 +0200
> Subject: [PATCH] factor: --exponents:
On 4/27/22 20:42, Pádraig Brady wrote:
> On 27/04/2022 19:36, Pádraig Brady wrote:
>> On 27/04/2022 18:21, Bernhard Voelker wrote:
>>> Finally, regarding '-e': is there any precedence (or a clashing option) in
>>> any other
>>> factor(1) implementation?
>&g
On 4/27/22 16:14, Pádraig Brady wrote:
> On 27/04/2022 11:07, Rasmus Villemoes wrote:
>> When factoring numbers that have a large 2^n factor, it can be hard to
>> eyeball just how many 2's there are. Add an option to print each prime
>> power factor in the x^y format (omitting the exponent when it
u want AT_NO_AUTOMOUNT in each fstatat call.
The attached fixes it.
Have a nice day,
BernyFrom d44f2a80f3c7d38845eb56148c3c0fd92668c5db Mon Sep 17 00:00:00 2001
From: Bernhard Voelker
Date: Thu, 7 Apr 2022 18:59:16 +0200
Subject: [PATCH] maint: remove obsolete statat gnulib module
* bootstrap.conf (gnulib_m
On 3/8/22 18:44, Paul Eggert wrote:
> On 3/8/22 04:29, Bernhard Voelker wrote:
>> I'm not so sure about that: at least in container environment it seems to be
>> common practice to mount regular files somewhere into the container, e.g.:
>
> Oh, I wasn't aware of that. Howe
On 3/7/22 20:09, Paul Eggert wrote:
> Although it's possible to mount onto a
> non-directory, this is bad practice and I don't think we need to worry
> about that.
I'm not so sure about that: at least in container environment it seems to be
common practice to mount regular files somewhere into
On 2/9/22 20:14, Nikos Papaspyrou wrote:
> [...] I want the input
> (or the contents of FILE) to go to the standard output untouched. The
> filtered input should only go to FILE1 and FILE2.
So the original example is possible with the process substitution you already
mentioned, e.g. with tr(1):
On 2/9/22 04:27, Nikos Papaspyrou wrote:
> Notice that the LOG file contains more than can be seen in the standard
> output. Three lines were printed with progress information, each starting
> with a carriage return character (0d). Only the last one remained and can
> be seen in the standard
On 2/1/22 19:12, Pádraig Brady wrote:
> I pushed a slightly adjusted wording of that in your name.
Thanks!
Have a nice day,
Berny
tag 53674 notabug
close 53674
stop
On 2/1/22 03:38, Alexandre Louisdhon wrote:
> Error- tail: unrecognized file system type 0x794c7630 for
> ‘/var/log/syslog’.
Thanks for the report.
That docker image seems to use a quite old coreutils version:
overlayfs - commonly used with Docker containers
older cksum would not be surprised.
Thanks, this is really useful.
As this is a user-visible change, this seems to warrant a NEWS entry.
Suggestion attached.
Have a nice day,
BernyFrom b1bdde90f60db4213ea01297b4d8b5f26bf954cf Mon Sep 17 00:00:00 2001
From: Bernhard Voelker
Date: Tue, 1 Feb 2022 06:0
On 1/15/22 21:27, Paul Eggert wrote:
> I installed commit f39a02a744ae97f6879ba1d20a528192772773e0 to try to fix the
> bugs.
Thanks, now the build incl. all tests pass here again.
Have a nice day,
Berny
This is a technical list where the replies are inline or at the bottom,
i.e., no top-posting.
On 1/14/22 18:01, Billa Surendra wrote:
> On Fri, 14 Jan, 2022, 10:27 pm Bernhard Voelker,
> wrote:
>> Do you cross-compile? Does running 'src/cp --help' on that build host work?
>
On 1/13/22 21:03, Paul Eggert wrote:
> I installed the attached so that GNU 'cp' now uses directory-relative
> syscalls like 'openat', 'mkdirat' and 'chmodat' when the target is a
> directory. The idea is to make it easier to modify 'cp' in the future so
> that it can use xfts for recursive
On 1/14/22 16:52, Billa Surendra wrote:
> On Fri, 14 Jan, 2022, 7:27 pm Pádraig Brady, wrote:
>> On 13/01/2022 11:35, Billa Surendra wrote:
>>> I am trying to install coreutils-9.0 version on my RISC-V Linux machine
>> but
>>> it's giving an error. Can anyone please help me to solve this
tag 53212 notabug
close 53212
stop
On 1/12/22 17:59, Joachim Wagner wrote:
> Not sure whether this is coreutils or kernel. Maybe both.
>
> A filesystem's device number such as reported by `stat` can be derived from
> major and minor of the underlying block device, e.g. xfs, or be allocated at
On 1/12/22 16:35, Joachim Wagner wrote:
> I cloned git://git.sv.gnu.org/coreutils to add a sentence on this to stat's
> man page but coreutils/man/stat.x is only a template, missing what I see in
> `man stat` on my system. Trying to find out how to contribute to
> documentation, I encountered
On 1/12/22 12:19, zendas via GNU coreutils Bug Reports wrote:
> I have considered dealing with this problem directly with three bytes
> instead, but I have two doubts, I can correctly use wc -m to recognize the
> bytes in the same environment (but cut can't?), and my script goal is to
>
On 12/22/21 18:15, Jim Meyering wrote:
> Thanks. Please push.
Thanks for the review, done:
https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=1435e8e5c5
> I like the idea of adding a syntax-check rule for that, too. Long overdue.
> However, what do you think about making it work also for
le which doesn't propagate errors
sc_prohibit_colon_redirection:
@cd $(srcdir)/tests && GIT_PAGER= git grep -En ': *>.*\|\|' \From 1435e8e5c51a9d7bb38b7a337058d80a8b78d79a Mon Sep 17 00:00:00 2001
From: Bernhard Voelker
Date: Mon, 20 Dec 2021 23:13:36 +0100
Subject: [PATCH] maint: updat
On 11/26/21 13:23, Frank Busse wrote:
> I tried it several times with checking the timestamps/md5sums of the
> files but after remounting the stick it doesn't happen anymore?! I
> guess it was a hiccup somewhere else in the system, sorry.
Perhaps the USB stick was removed from the system before
On 11/26/21 00:10, Warren Parad wrote:
> On Fri, Nov 26, 2021 at 12:02 AM Bernhard Voelker <mailto:m...@bernhard-voelker.de>> wrote:
>> The synopsis is already complex and confusing enough:
>
> Opinion, it is as complex as it allows, sounds like you are saying "
On 11/25/21 18:53, Warren Parad wrote:
> It is too frequent a problem to know which is the correct order of TARGET
> and LINK_NAME.
I disagree: it is a one-time effort to learn the order ... similar as
for mv(1) and cp(1).
> Since the command already believes that it can't create a link to a
tag 52033 notabug
close 52033
stop
On 11/22/21 14:39, Visser, Gerard wrote:
> Please close the case.
Hereby done.
On 10/22/21 16:21, Pádraig Brady wrote:
> Thanks for all the input.
> I've now pushed the following to address this:
>
> https://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=f60a3981c
>
> Notes:
> - Brevity in --help and man pages is a feature
> - I kept the existing NOTE: style in
On 10/21/21 15:14, Florent Flament wrote:
> Pádraig Brady writes:
>> +NOTE: printf(1) is a preferred alternative, with more standard option
>> handling.\
> I believe that it misses the point. It is still not clear that the echo
> command doesn't behave as one would expect for a few edge cases.
On 10/10/21 19:57, Pádraig Brady wrote:
>sort: numbers use ‘.’ as a decimal point in this locale
What about adding the hint to that message that this an "ambiguity warning"?
sort: ambiguity warning: numbers use ‘.’ as a decimal point in this locale
(Likewise for the other cases, of
On 9/26/21 14:52, Pádraig Brady wrote:
* doc/coreutils.texi (ls invocation - general output formatting):
The option ordering was not changed when the option was renamed
from --null to --zero.
good catch, thanks!
Have a nice day,
Berny
On 9/24/21 22:02, Pádraig Brady wrote:
Tested equivalent patch is attached.
Nice small patch.
Maybe it's worth documenting in the enum where the "bad range" starts against
which the
code later tests?
Furthermore, I think it's worth adding a NEWS entry and mentioning that this
bug has been
On 9/20/21 23:52, Pádraig Brady wrote:
We plan to release coreutils-9.0 in the coming week
so any testing you can do on various different systems between now and then
would be most welcome.
--
You can download the coreutils snapshot in xz format (5.3 MB)
On 9/9/21 17:01, Pádraig Brady wrote:
> If one updated getopt/argmatch to support something like:
>
>prog=$(cksum --?algo=md5 && echo 'cksum -a md5' || echo 'md5sum')
>
> That would be a bit more elegant, but less widely supported.
>
> Anyway all this is a general issue,
> that cksum shouldn't
On 9/5/21 07:37, Peng Yu wrote:
> I got 1 instead of 2 in the following example. How to count the last
> even when it does not end with a newline character? Thanks.
>
> $ printf 'a\nb'|wc -l
> 1
A text file (in contrast to a binary file) must end on a newline character,
otherwise the remainder
On 8/25/21 10:38 AM, Jim Meyering wrote:
> * cfg.mk (exclude_file_name_regexp--sc_system_h_headers):
> Add find-mount-point.h to the regexp.
+1
even better, thanks.
Have a nice day,
Berny
1 - 100 of 1535 matches
Mail list logo