On Wed, Dec 27, 2023 at 8:20 AM Pádraig Brady wrote:
> On 17/12/2023 14:17, Pádraig Brady wrote:
> > On 16/12/2023 22:01, Bernhard Voelker wrote:
> >> 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 th
Thanks. Nice improvement.
I compared --help and --version output, which showed no difference
other than the intended ones.
make check passed, modulo this unrelated failure on Fedora 38:
numfmt.pl: test lcl-dbl-to-human-1: stdout mismatch, comparing
lcl-dbl-to-human-1.1 (expected) and lcl-dbl-to-h
On Wed, Dec 27, 2023 at 4:14 PM Pádraig Brady wrote:
> On 27/12/2023 20:52, Jim Meyering wrote:
> > Thanks. Nice improvement.
> > I compared --help and --version output, which showed no difference
> > other than the intended ones.
>
> Thanks for the review. Pushed.
On Wed, Feb 28, 2024 at 9:09 AM Pádraig Brady wrote:
> >> On 11/30/23 12:11, Pádraig Brady wrote:
> >>> Though that will generally give 128K, which is good when processing all
> >>> of a file,
> >>> but perhaps overkill when processing just the last part of a file.
> >>
> >> The 128 KiB numb
On Thu, Jul 4, 2024 at 1:36 AM Pádraig Brady wrote:
>
> On 04/07/2024 02:08, Collin Funk wrote:
> > Hi,
> >
> > Recently there was a bug fix in Gnulib's tests/init.sh. I then noticed
> > many packages copy this manually from Gnulib. Bruno and I discussed the
> > proper way to import the file from
Stefano Lattarini wrote:
> On 08/31/2012 09:59 PM, Jim Meyering wrote:
>> Jim Meyering wrote:
>>> Jim Meyering wrote:
>>> ...
>>>> No problem.
>>>> Next step, "make distcheck". First failure is because inclusion of
>>>
Stefano Lattarini wrote:
> This is a re-spin, extension and follow-up to this previous series:
>
> <http://lists.gnu.org/archive/html/coreutils/2012-08/msg00257.html>
>
> plus other follow-up fixlets and refactoring. Thanks to Jim Meyering
> for his testing of ea
Stefano Lattarini wrote:
> On 09/01/2012 01:46 AM, Stefano Lattarini wrote:
>>
>> Subject: maint: avoid distcheck failure by properly cleaning $(EXTRA_MANS)
>>
> Erm, it should be s/$(EXTRA_MANS)/$(ALL_MANS)/ here.
Amended. Thanks.
Stefano Lattarini wrote:
> On 09/01/2012 08:39 AM, Jim Meyering wrote:
>>
>> [SNIP]
>>
>> However, if you have something that looks good for automake, please
>> post a patch.
>>
> Should be done as [PATCH 21/22] of my new series:
>
> <
Stefano Lattarini wrote:
> On 09/01/2012 10:20 AM, Stefano Lattarini wrote:
>> On 09/01/2012 10:08 AM, Jim Meyering wrote:
>>> Stefano Lattarini wrote:
>>>> This is a re-spin, extension and follow-up to this previous series:
>>>>
>>>>
Stefano Lattarini wrote:
> On 09/01/2012 10:40 AM, Jim Meyering wrote:
>>
>> I like your changes, and for now am mainly concerned with ensuring
>> that "make distcheck" continues to work with them.
>> If you find an actual problem or a way to eliminate th
Jim Meyering wrote:
...
>> FYI, here's another make distcheck problem,
...
> And here's another:
...
> make[3]: Makefile: No such file or directory
> make[3]: *** No rule to make target `Makefile'. Stop.
> make[3]: Entering directory
> /h/j/w/co/cu/te
Stefano Lattarini wrote:
> From: Jim Meyering
>
> * man/local.mk (distclean-local): Remove $(ALL_MANS) when doing
> a VPATH build. If it's not done, generated manpages can be left
> around in the build directory after a "make distclean", causing
> failures
Jim Meyering wrote:
> Stefano Lattarini wrote:
>
>> From: Jim Meyering
>>
>> * man/local.mk (distclean-local): Remove $(ALL_MANS) when doing
>> a VPATH build. If it's not done, generated manpages can be left
>> around in the build directory after a "
Stefano Lattarini wrote:
> Oh, and now that I notice ...
>
> On 09/01/2012 01:46 AM, Stefano Lattarini wrote:
>> Some of them can be simplified after the previous changes, some
>> of them have been downright broken them, and need fixing.
>>
>> * src/local.mk: Adjust some comments.
>> (EXTRA_DIST):
s gone). Simply define this to the sorted
> contents of $(bin_PROGRAMS), with the 'src/' prefix and the $(EXEEXT)
> suffix (if any) removed. Reported by Jim Meyering.
>
> Reported-by: Jim Meyering
I'm making this additional change to your log message:
- suffix (
Jim Meyering wrote:
...
>> With this (final?) change, I expect "make distcheck" to succeed
>> using my current set of patches.
>
> Not quite:
...
> And fixed by this:
>
> Subject: [PATCH] build: restore handling of space-tainted build directory
> name
similarity to what is done for $(EXTRA_MANS)
>>
> I'd substitute this sentence with:
>
> This is similar to what is done for $(EXTRA_MANS), thus
> improving consistency and readability.
I prefer that, too.
...
>> [PATCH 19/25] maint: port manpages generation to
Stefano Lattarini wrote:
>> [PATCH 22/25] build: create src/ and man/ via configure
>>
>> * configure.ac: Create man/ and src/, since, now that there is no
>> generated Makefile in each, the directory will not exist in a
>> non-srcdir build.
>>
> This patch can be dropped AFAICS: 'man/' is created
Jim Meyering wrote:
> Erik Auerswald wrote:
...
>>> Good point. Thanks. I'm tempted to remove the build instructions from
>>> README-prereq, and instead to include my autotools-install script under
>>> script and referencing it. WDYT?
>>
>> I pre
e58207ee331ffa Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Sun, 2 Sep 2012 13:42:39 +0200
Subject: [PATCH] maint: accommodate upcoming, expanded list of warnings from
gnulib
* configure.ac: Disable a new gcc warning, -Wsuggest-attribute=format,
since it triggers on copy.c (which I'm
er_name_utf8_requires_ICONV
>
> However, the syntax-check succeeds.
Thanks for the report.
Here's the fix that I first wrote a day or so ago,
but somehow managed not to include in the series I pushed:
>From 135664d25e09d9b285b59012832f0e8db5802042 Mon Sep 17 00:00:00 2001
From: Jim M
Stefano Lattarini wrote:
> * scripts/autotools-install: Here, honouring $MAKE. This might be
> useful on systems where the make implementation available in $PATH
> by default is limited (Solaris) or broken (HP-UX).
Thanks.
I've applied both this and your other autotools-install patch.
In each ca
Stefano Lattarini wrote:
> Plus some other preparatory, follow-up or "while-at-it" changes.
>
> After this, "make syntax-check" and "make distcheck" still pass on
> my Debian box.
>
> This completes the first important part of the "de-recursion" of the
> coreutils build system: the compilation of t
Jim Meyering wrote:
> Stefano Lattarini wrote:
>> Plus some other preparatory, follow-up or "while-at-it" changes.
>>
>> After this, "make syntax-check" and "make distcheck" still pass on
>> my Debian box.
>>
>> This complet
://www.gnu.org/software/automake/manual/automake.html#Parallel-Test-Harness>
Thanks for the explanation, but running the commands you suggest generates
over 200 hundreds of lines of output, all but one or two of which are
irrelevant to me. Running the technically-unsupported command produces
precisel
Stefano Lattarini wrote:
> On 09/04/2012 12:58 PM, Jim Meyering wrote:
>> Stefano Lattarini wrote:
>> ...
>>>> I still haven't reviewed your changes, but in using them I did notice
>>>> a missing dependency:
>>>>
>>>> I ran
Stefano Lattarini wrote:
> * tests/init.cfg (stty_reversible_init_): Quote '$abs_top_srcdir'
> properly.
> (fiemap_capable_): Quote '$abs_srcdir' properly.
> (require_dirent_d_type_): Likewise.
> ---
> init.cfg | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/init.cfg
Andreas Schwab wrote:
> Jim Meyering writes:
>
>> Stefano Lattarini wrote:
>>> * tests/init.cfg (stty_reversible_init_): Quote '$abs_top_srcdir'
>>> properly.
>>> (fiemap_capable_): Quote '$abs_srcdir' properly.
>>> (require_dir
Stefano Lattarini wrote:
> On 09/04/2012 05:25 PM, Jim Meyering wrote:
>>
>> Hi Stefano,
>>
>> I'm done reviewing.
>> Here's the 17-cset series I'm ready to push.
[For anyone wondering about the message to which Stefano has
just replied, it was d
Stefano Lattarini wrote:
> On 09/04/2012 06:03 PM, Jim Meyering wrote:
>> Stefano Lattarini wrote:
>>> On 09/04/2012 05:25 PM, Jim Meyering wrote:
>>>>
>>>> Hi Stefano,
>>>>
>>>> I'm done reviewing.
>>>> Here'
Bernhard Voelker wrote:
> What about making --enable-gcc-warnings the default
> for CU developers, i.e. when .git exists?
Good idea.
If someone has gone to the trouble of building from cloned sources
they're probably also using modern enough tools.
Do you feel like writing the patch?
Pádraig Brady wrote:
> * src/nproc.c (main): Error if any non option parameters.
> * NEWS: Mention the change in behavior.
> ---
> NEWS|4
> src/nproc.c |7 +++
> 2 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/NEWS b/NEWS
> index 63fa042..995fafb 100644
Jim Meyering wrote:
> Ondrej Oprala wrote:
>> here's the new patch...I hope it's all alright now.
>> And sorry about not mentioning Bernhard in the first place,
>> it just didn't occur to me.
> ...
>> Subject: [PATCH] tests: Add error checking for root-
Pádraig Brady wrote:
> On 09/06/2012 11:09 AM, Jim Meyering wrote:
>> diff --git a/NEWS b/NEWS
>> index 63fa042..6941721 100644
>> --- a/NEWS
>> +++ b/NEWS
>> @@ -25,6 +25,12 @@ GNU coreutils NEWS -*- outline -*-
>>
>> ** Improvements
>>
>
Eric Blake wrote:
> On 09/06/2012 01:11 AM, Bernhard Voelker wrote:
>> On September 6, 2012 at 8:39 AM Jim Meyering wrote:
>>
>>> Bernhard Voelker wrote:
>>>> What about making --enable-gcc-warnings the default
>>>> for CU developers, i.e. when .g
Bernhard Voelker wrote:
> On September 6, 2012 at 4:31 PM Eric Blake wrote:
>
>> $ echo one > bar
>> $ echo two > blah
>> $ cp -n blah bar
>> $ echo $?
>> 0
>> $ cat bar
>> one
>>
>> that FreeBSD also returns 0 in this case, and I don't want to break
>> interoperability. Therefore, I'm going to c
Ondrej Oprala wrote:
> On 09/06/2012 12:09 PM, Jim Meyering wrote:
>> I'll push this once you ACK it:
> Hi,
> it's all ok with me, thanks for taking the time.
Rats! Both of us missed the fact that I changed the "Author:"
from your name to mine. Grr... Terribl
I've converted lib/ to non-recursive make, too, and thought it was time
to measure the performance change. For now, it's all in a single ugly
commit, so I'm not ready to share. I will tease it into at least a few
separate commits so that it's easier to review.
I didn't expect much improvement, s
Stefano Lattarini wrote:
> On 09/08/2012 03:29 PM, Jim Meyering wrote:
>>
>> But, ... surprise! So far there is *no* improvement, and in fact a small
>> penalty in this very worst case:
>>
> My wild guess is that the culprit for this might be the Automake-generated
Stefano Lattarini wrote:
> On 09/08/2012 07:46 PM, Jim Meyering wrote:
>> Stefano Lattarini wrote:
>>> On 09/08/2012 03:29 PM, Jim Meyering wrote:
>>>>
>>>> But, ... surprise! So far there is *no* improvement, and in fact a small
>>>> pena
Jim Meyering wrote:
...
> On the subject of converting to non-recursive make in lib/,
> I have at least one problem so far: how can I select different
> CFLAGS depending on the directory containing the file I'm compiling?
>
> As you know, we currently have three differ
Jim Meyering wrote:
> Jim Meyering wrote:
> ...
>> On the subject of converting to non-recursive make in lib/,
>> I have at least one problem so far: how can I select different
>> CFLAGS depending on the directory containing the file I'm compiling?
>>
>
t
same-inode
configure.ac:
-gl_ROOT_DEV_INO
Makefile.am:
+lib_SOURCES += root-dev-ino.c root-dev-ino.h
Include:
"root-dev-ino.h"
--
1.7.12.289.g0ce9864
>From c424de16b1c8607f2caa7c85d69196f9d8e3a103 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Sat, 8 Sep 2012 15:11:20 +0200
Unlikely ever to have mattered, but still...
>From e571cfd9c7f035886182100b7a5e27ad7d48f1ca Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Sun, 9 Sep 2012 19:23:11 +0200
Subject: [PATCH] build: fix a minor man-page generation dependency error
* man/local.mk (man/dir.1): Depend on src/
We can't have build-from-tarball requiring perl (via help2man)
or regenerating a distributed .1 file when its .c file has not changed.
>From 57da212a95054cc230ffb00f38ea655c798926f8 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Sun, 9 Sep 2012 19:27:25 +0200
Subject: [PATCH] build
Stefano Lattarini wrote:
> Hi Jim.
>
> On 09/10/2012 09:41 AM, Jim Meyering wrote:
>> We can't have build-from-tarball requiring perl (via help2man)
>> or regenerating a distributed .1 file when its .c file has not changed.
>>
>> From 57da212a95054cc230ffb0
Stefano Lattarini wrote:
> On 09/10/2012 12:46 PM, Jim Meyering wrote:
>> Stefano Lattarini wrote:
>>> Hi Jim.
>>>
>>> On 09/10/2012 09:41 AM, Jim Meyering wrote:
>>>> We can't have build-from-tarball requiring perl (via help2man)
>>&g
Stefano Lattarini wrote:
...
> Just out of curiosity: is [test FILE -nt OTHER_FILE] a feature in POSIX?
Not in any current standard.
> Anyway, maybe it could be emulated with "find -newer" or something
> similar...
Sure, but not worth it, because some find programs probably lack support
for the
FYI,
>From d9bc0d0d22b159f1a0b2cb11d4efd759921da238 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Mon, 10 Sep 2012 11:00:35 +0200
Subject: [PATCH] maint: gen-lists-of-programs.sh: improve comments
* build-aux/gen-lists-of-programs.sh: Improve comments.
---
build-aux/gen-lists
FYI,
>From 4fdd1cc597209b9e85ed66fdb594abca6f148155 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Sat, 8 Sep 2012 21:17:32 +0200
Subject: [PATCH] maint: allow per-directory CFLAGS settings with
non-recursive make
* src/local.mk (AM_CFLAGS): Don't use $(WARN_CFLAGS) here.
Here are three patches that extend coreutils' non-recursive
build into lib/, too. With these, "make distcheck" still passes:
Makefile.am | 10 -
bootstrap.conf|5
configure.ac |1
gl/buil
Pádraig Brady wrote:
> In support of the upcoming `df --output` and
> $cmd --help auto alignment changes, the attached
> patch gives more formatting control to callers of mbsalign().
Thanks. I've tested that, and it passed.
> Subject: [PATCH] maint: add more control flags to mbsalign
>
> * gl/li
Bernhard Voelker wrote:
> On September 10, 2012 at 1:41 PM Jim Meyering wrote:
>
>> I want each *existing* .1 file to depend solely on its corresponding .c file.
>> However, when a .1 file does not exist, *then* I want it to depend on
>> its corresponding executable.
>
Bernhard Voelker wrote:
> On September 10, 2012 at 4:34 PM Jim Meyering wrote:
>
>> diff --git a/build-aux/gen-lists-of-programs.sh
>> b/build-aux/gen-lists-of-programs.sh
>> index 9ca46cf..de9ff64 100755
>> --- a/build-aux/gen-lists-of-programs.sh
>> +++
Stefano Lattarini wrote:
> * configure.ac: Here, by adding a missing '*' to the wildcard in
> a 'case' construct over the contents of $PERL.
> ---
>
> Such a gross blunder (which was a mistake of mine, BTW *blush*) shows
> that 'my-distcheck' should probably be improved to configure and build
>
9)) > /dev/null
7.96
Using the seq program from coreutils-8.19 took almost 10 minutes:
$ env time --f=%e seq $((10**9)) > /dev/null
597.92
Here's the patch:
>From f7a09b702025b39f566c9e00bdf4226e37ee3912 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Thu, 13 Sep 2012
ot; prefix)
make check TESTS=tests/df/header.sh SUBDIRS=.
> d. 'make check' of a certain test fails:
Use the syntax shown above.
...
> e. 'make check' of a certain test subsequently fails in gnulib-tests:
...
The SUBDIRS=. part excludes gnulib-tests/
Hey! Here
Jim Meyering wrote:
> Inspired by Pádraig's April-fools post,
> http://thread.gmane.org/gmane.comp.gnu.coreutils.general/972
> and spurred by the fact that Torbjorn and Niels had to roll
> their own seq-like program to test their new factoring code
> (http://gmplib.org:800
Jim Meyering wrote:
...
> Hey! Here's an even better idea:
This is the same, but also passes make syntax-check.
I had to exempt the new tests/GNUmakefile from the
sc_prohibit_tab_based_indentation rule.
>From 5fba24985d45660a27dace2f19062247871528d8 Mon Sep 17 00:00:00 2001
From: J
Bernhard Voelker wrote:
> On 09/14/2012 08:54 AM, Jim Meyering wrote:
>
> Real fast now!
>
>> +static bool
>> +seq_fast (char const *a, char const *b)
>> +{
>
>> [...]
>
>> + char *buf = xmalloc (N * (n + 1));
>
> Shouldn't we free(b
Bernhard Voelker wrote:
> On 09/14/2012 10:40 AM, Jim Meyering wrote:
>> Bernhard Voelker wrote:
>>> Shouldn't we free(buf), too?
>>
>> Thanks.
>> Yes, to placate leak-checking tools, but for the record, any time buf
>> was allocated, we
Pádraig Brady wrote:
> On 09/12/2012 03:31 AM, Pádraig Brady wrote:
>> I found a more reliable way to disable core dumps,
>> so another attempt at this is attached.
>
> V2 attached, which factors out a disable_core_dumps() function.
Good idea.
> Subject: [PATCH] timeout: handle signals more tran
Pádraig Brady wrote:
> I just did this and noticed that seq from
> my system rather than the just build seq was used.
>
> make check TESTS=tests/misc/seq.pl SUBDIRS=.
>
> I'll look later tonight, but someone might
> know off the top of their heads what the issue is.
Hi Pádraig,
Thanks for testi
Pádraig Brady wrote:
> I just did this and noticed that seq from
> my system rather than the just build seq was used.
>
> make check TESTS=tests/misc/seq.pl SUBDIRS=.
>
> I'll look later tonight, but someone might
> know off the top of their heads what the issue is.
I have found *a* problem, and
:
>From f6a83d0a9e0e4d87f5e2db91d0efd717f132dbd2 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Fri, 14 Sep 2012 18:19:39 +0200
Subject: [PATCH] build: don't prefix the RHS of "GPERF = ..." with "lib/"
* gl/build-aux/prefix-gnulib-mk (prefix_assignment): Exempt
the RHS of a "GP
Pádraig Brady wrote:
> On 09/14/2012 04:54 PM, Jim Meyering wrote:
>> Pádraig Brady wrote:
>>> I just did this and noticed that seq from
>>> my system rather than the just build seq was used.
>>>
>>>make check TESTS=tests/misc/seq.pl SUBDIRS=.
>&
[Stefano, FYI, I have to revert the change of yours
that made coreutils switch to using AM_TESTS_ENVIRONMENT. ]
Jim Meyering wrote:
...
> That's the error.
> 1.11.3 is inadequate, since we're using AM_TESTS_ENVIRONMENT,
> and 1.11.3 has this code in am/check.am:
>
>
Pádraig Brady wrote:
> On 09/14/2012 06:40 PM, Jim Meyering wrote:
>
>> I expect to apply this:
>
>> diff --git a/tests/local.mk b/tests/local.mk
>
>> -AM_TESTS_ENVIRONMENT = \
>> +TESTS_ENVIRONMENT = \
>
Pádraig Brady wrote:
...
> How about the attached follow up to enable the
> fast code in more cases?
Thanks!
I much prefer to honor --separator=S and your adjustment to use optind.
...
> Subject: [PATCH] seq: enable the fast integer printing code in more cases
>
> * src/seq.c (main): Adjust the i
re.
>From c5ccf29bbfaab01ed893c9ca3a3843181c329317 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Sat, 15 Sep 2012 08:09:18 +0200
Subject: [PATCH] doc: update seq description
* doc/coreutils.texi (seq invocation): Update an example and mention
that with the new constraints, seq can print arbitrarily large numb
Torbjorn Granlund wrote:
> For general seq use, I suppose we should do away with `incr' and instead
> use a general `add'. Below is a suggested implementation, and as bonus
> also a `sub'.
>
> Like `incr', `add' needs an extra byte if space, since if the end value
> is within the increment from a
Mike Frysinger wrote:
...
>> I have mixed feelings. If someone is modifying sources and expecting
>> to be able to rebuild, they'd better have developer tools like perl.
>>
>> On the other hand, I dislike distributing a deliberately hamstrung
>> Makefile.in, even though this wart is only in a gene
Here's a NEWS entry for the conversion to non-recursive make:
>From c8ed1909e1e5fd4154681be58674c670730dc926 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Sun, 16 Sep 2012 21:46:17 +0200
Subject: [PATCH] doc: NEWS: mention the conversion to non-recursive make
* NEWS (Build-related):
Bernhard Voelker wrote:
> On 09/18/2012 02:54 PM, Bernhard Voelker wrote:
>> Here's a try.
>
> oops, sorry. I removed the wrong word in the texi file.
>
> Here's a better one.
>
>>From 39ea828e94e8232660f83c62e1eff85026070b4c Mon Sep 17 00:00:00 2001
> From: Benno Schulenberg
> Date: Tue, 18 Sep 2
Pádraig Brady wrote:
> On 09/18/2012 02:21 PM, Jim Meyering wrote:
>> + was seen when running parallel "make check".
>
> s/check/syntax-check/ ?
Yes, thanks. Good catch. Corrected.
FYI,
>From 9228b861cc230667e069f3c573150a014c6512ad Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Tue, 18 Sep 2012 16:29:49 +0200
Subject: [PATCH] maint: make the tight-scope syntax-check rule work again
* cfg.mk: Configure a few variable to make the tight-scope rule work.
* gnulib: Upd
Something on rawhide changed to make this test consume more virtual memory.
A month or two ago, it would pass, but now, even with 21,000 KiB of VM,
it would fail. So I've increased the limit to 22,000 KiB.
>From 87af2e09225c9cf4a639736f0d82f16be6ec6707 Mon Sep 17 00:00:00 2001
From: Jim
I noticed that there were two newly-failing rm-related tests on Solaris 10.
Here's the fix:
>From 623add906d554434a232d890c92b5e4ff21a1d47 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Wed, 19 Sep 2012 09:35:12 +0200
Subject: [PATCH] rm: be even more careful when using a replaceme
FYI, no semantic change:
>From 958bef88f9a0471544d2ff4826e7e6d0483e9b1b Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Thu, 20 Sep 2012 17:47:25 +0200
Subject: [PATCH] build: move non-recursive-gnulib-prefix-hack to gnulib;
update
I've moved the non-recursive-gnulib-prefix-hack m
Bernhard Voelker wrote:
> Finally, I made it the whole long way to df's new --output option.
> Example use:
>
> $ src/df --o=target,ipcent,pcent .
> Mounted on IUse% Use%
> /media/sdb55% 75%
>
> The discussion about it started with http://bugs.gnu.org/10915.
>
> The biggest changes are
Bernhard Voelker wrote:
> On 09/21/2012 09:34 AM, Jim Meyering wrote:
>> Bernhard Voelker wrote:
...
>> One nit: in NEWS (in 19/20), when a period is not at the end of the line,
>> put two spaces after it, not just one. Same thing in --help output.
>
> I wonder if sy
Bernhard Voelker wrote:
> On 09/21/2012 11:28 AM, Jim Meyering wrote:
>> Bernhard Voelker wrote:
>>> I wonder if syntax-check couldn't prevent this ... didn't we have this
>>> already a few weeks ago?
>>
>> Good idea.
>> It's definitely
Bernhard Voelker wrote:
> On 09/21/2012 12:15 PM, Jim Meyering wrote:
>> Bernhard Voelker wrote:
>>> Apropos: the syntax-check failed yesterday, when I tried to
>>> add the new test, because the test was not yet in the git history,
>>> but sc_tests_list
Bernhard Voelker wrote:
> On 09/21/2012 12:36 PM, Jim Meyering wrote:
>> Bernhard Voelker wrote:
>>> On 09/21/2012 12:15 PM, Jim Meyering wrote:
>>>> Bernhard Voelker wrote:
>>>> If you merely "git add" your new test script, that should be en
Ondrej Oprala wrote:
> On 08/07/2012 05:37 PM, Bernhard Voelker wrote:
>> On 08/07/2012 05:01 PM, Ondrej Oprala wrote:
>>> Hi, I've renamed the variable to be more hinting of it's purpose
>>> and --no-preserve=mode should now work properly with directories
>>> as well.
>>> Cheers,
>>> Ondrej
>>
Bernhard Voelker wrote:
> Just a status update:
> I have to move the code around a bit for Padraig's suggestions
> * to print "total" instead of a "-" in the target field if the
> source field is unused, dash-in-the-target-field
> * to not permit the abbreviation of field names.
>
> It seems that
Voelker, Bernhard wrote:
> Robert Milasan wrote:
>
>> That has been fixed, at least in 12.1 and 12.2 (even if it's not fixed
>> there is not rootfs entry in /proc/self/mountinfo):
>
> I know.
> The problem is that mount from util-linux has it's own
> wrapper for the mount entries which is using mo
Ondrej Oprala wrote:
...
> The .explicit_no_preserve_mode flag should now be turned off when
> --preserve=all
> is run into.
> I've also added a test for the mixed options next to other tests in
> preserve-mode.sh.
...
> Subject: [PATCH] cp: Fix the --no-preserve=mode option
>
> * NEWS: Mention th
FYI, I noticed this today on the go IRC channel, #go-nuts:
[05:14-10/01] when I use this
https://github.com/shanemhansen/gocryptodev on arm devices with
crypto hardware, go can beat coreutils sha1sum and openssl. <<<
Pretty nice
among the dependents of $(BUILT_SOURCES),
and there is currently no way to stage the building of those
dependents. Building them out of order is fatal, usually ending
with link failures due to undefined rpl_* symbols.
>From 852930e88a263bb2e6a6e328dfc7af081637e5cc Mon Sep 17 00:00:00 2001
From:
Robert Milasan wrote:
> On Wed, 3 Oct 2012 11:18:59 -0600
> "Bob Proulx" wrote:
>
>> What version of tail are you using?
>>
>> tail --version
>>
>> I think the easiest way to see what is happening at run time is to use
>> strace. Install it if you don't have it. Then run:
>>
>> cat /etc/pas
Robert Milasan wrote:
> On Wed, 03 Oct 2012 20:09:26 +0200
> "Jim Meyering" wrote:
>
>> There is some documentation on the effects of that variable
>> in "info coreutils":
>>
>> 2.13 Standards conformance
>>
Robert Milasan wrote:
> On Thu, 04 Oct 2012 10:14:15 +0200
> "Jim Meyering" wrote:
>
>> You can check by seeing how lib/posixver.c is compiled or by running
>> a command like the following. Here's what I see on Fedora 17 and
>> newer:
>>
>
Philipp Thomas wrote:
> Jim,
>
> * Jeff liu (jeff@oracle.com) [20110418 15:54]:
>
>> FYI, I once implemented a similar patch to teach du(1) to show the disk
>> footprint with reflinked stuff for OCFS2 only.
>>
>> It is make use of rb-tree to figure out the shared extents and
>> calculate the ex
FYI,
>From f947735d3c4036703e03bf6970784430db1355f7 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Fri, 5 Oct 2012 22:35:27 +0200
Subject: [PATCH] build: avoid link failure when strerror is replaced
When building the new make-prime-list program on a system for which
strerror is defined
d as errors
make[2]: *** [src/factor.o] Error 1
I'm sure there's a cleaner way to fix it, but this is
good enough for now.
>From 231e40a6ba29b892daca1e4a2e464c315874e155 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Sun, 7 Oct 2012 10:37:25 +0200
Subject: [PATCH] maint: avoid warni
Pádraig Brady wrote:
> In the recent factor rewrite, the GMP code
> wasn't actually used; just an error was printed
> on integer overflow. While fixing that it was noticed
> that correct input validation wasn't done in all cases
> when falling back to the GMP code.
>
> * src/factor.c (print_factor
Jim Meyering wrote:
> Pádraig Brady wrote:
>> In the recent factor rewrite, the GMP code
>> wasn't actually used; just an error was printed
>> on integer overflow. While fixing that it was noticed
>> that correct input validation wasn't done in all cases
Philipp Thomas wrote:
> * Jim Meyering (j...@meyering.net) [20121003 20:09]:
>
>> I can reproduce that by specifying an older version of POSIX:
>>
>> $ : | _POSIX2_VERSION=0 tail -c 10
>> tail: cannot open '10' for reading: No such file or direc
1 - 100 of 1574 matches
Mail list logo