Re: Bash vs. sh

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 4/22/2008 3:42 AM: > | I'll probably change the instructions in README-hacking to mention > | that you may have to run "bash ./bootstrap" rather than > | > | $ ./bootstrap > | >

retaining AFS-specific nameless group IDs (PAG) in `id' and `groups'

Jim Meyering <[EMAIL PROTECTED]> wrote: > Didi <[EMAIL PROTECTED]> wrote: >>> If by "unknown" you mean nameless, that's not what the patch does. >>> Such a patch would not even have been considered. >> >> I agree that hiding this inf

FYI: 3 small patches

nt.mk (sc_immutable_NEWS): New rule. (update-NEWS-hash): New rule to update the hard-coded hash. tests: ensure that all exec-$PERL lines are the same * maint.mk (sc_perl_coreutils_test): New rule. >From 79a98d9bc1ee67dadc8df376d336c4f1270c464d Mon Sep 17 00:00:00 2001 From: Jim

Re: [PATCH] md5sum+sha*sum: add option --quiet/-q to suppress OK messages

Erik Auerswald <[EMAIL PROTECTED]> wrote: > IMHO md5sum and sha*sum are too verbose by default, especially when > checking a large collection of files with only a few failing validation. > Therefore I'd like to see an option added to suppress just the output > for successfully verified files. > > T

Re: [PATCH] id should not show selinux context when user is specified

Ondřej Vašík <[EMAIL PROTECTED]> wrote: ... > +/* If true, id is used on specified user/group name */ > +static bool specified_name = false; > + > /* The real and effective IDs of the user to print. */ > static uid_t ruid, euid; > static gid_t rgid, egid; > @@ -170,7 +173,7 @@ main (int argc, ch

Re: [PATCH] md5sum+sha*sum: add option --quiet/-q to suppress OK messages

Erik Auerswald <[EMAIL PROTECTED]> wrote: > On Tue, Apr 22, 2008 at 06:05:48PM +0200, Jim Meyering wrote: >> Erik Auerswald <[EMAIL PROTECTED]> wrote: >> > IMHO md5sum and sha*sum are too verbose by default, especially when >> > checking a large coll

Re: [PATCH] Use a hash rather than a linked-list for cycle check in cp

"Bo Borgerson" <[EMAIL PROTECTED]> wrote: > This addresses a FIXME in src/copy.c: > > > -/* FIXME: rewrite this to use a hash table so we avoid the quadratic > - performance hit that's probably noticeable only on trees deeper > - than a few hundred levels. See use of active_dir_map in rem

Re: Bash vs. sh

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 4/22/2008 7:23 AM: > |> Is it worth writing bootstrap.m4sh, and running it through autom4te to get > |> the shell selection code from autoconf with minimal effort on your part? > |> You'd sti

Re: FYI: 3 small patches

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 4/22/2008 8:28 AM: > | Without a guard like this, it is far too easy to apply a patch > | prepared against a preceding release, and not notice that a NEWS > | entry is inserted into the wrong blo

Re: Bash vs. sh

"Joel E. Denny" <[EMAIL PROTECTED]> wrote: > On Tue, 22 Apr 2008, Jim Meyering wrote: > >> > as the preferred method for getting started, avoiding the need to check in >> > bootstrap? Or even have a two-level bootstrap: ./bootstrap is a simple >

Re: [PATCH] Use a hash rather than a linked-list for cycle check in cp

"Bo Borgerson" <[EMAIL PROTECTED]> wrote: > On Tue, Apr 22, 2008 at 3:03 PM, Jim Meyering <[EMAIL PROTECTED]> wrote: >> >> Hi Bo, >> >> Thanks for that patch. >> >> However, let's see if Cai Xianchao and Li Zefan >> are s

Re: FYI: 3 small patches

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 4/22/2008 8:28 AM: > | Without a guard like this, it is far too easy to apply a patch > | prepared against a preceding release, and not notice that a NEWS > | entry is inserted into the wrong blo

Re: [PATCH] Improve memory management in join

"Bo Borgerson" <[EMAIL PROTECTED]> wrote: > This improves the performance of `join' by reducing memory management > overhead and eliminating unnecessary copies for order checking: > > $ valgrind src/join.master ja jb > ==23744== malloc/free: 4,571,152 allocs, 4,571,152 frees, 255,971,774 > bytes al

Re: coreutils-6.11 released

Elbert Pol <[EMAIL PROTECTED]> wrote: > I try that build, but is fails now at a earlyer point. Well, your logs show that configure succeeded, which means the failure is _later_. And that means my patch solved the problem. > I attach logs Thank you. The first interesting part is here: In fi

Re: PATH and security

Bruno Haible <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> If security isn't enough of an argument, you can consider this yet another >> reason not to put "." early in your PATH. Please consider removing >> "." from your PATH altogeth

Re: Bash vs. sh

"Joel E. Denny" <[EMAIL PROTECTED]> wrote: > On Tue, 22 Apr 2008, Jim Meyering wrote: > >> "Joel E. Denny" <[EMAIL PROTECTED]> wrote: > >> There's already a bootstrap module in gnulib. > > You mean build-aux/bootstrap? Yes. >&

Re: PATH and security

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 4/22/2008 5:13 PM: > |>> If security isn't enough of an argument, you can consider this yet another > |>> reason not to put "." early in your PATH. Please consider removing > |>&

[Elbert Pol] Re: coreutils-6.11 released

Forwarding manually. --- Begin Message --- Hmmm hoi Jim, Thats indeed strange. I attach both files Jim Meyering wrote: Elbert Pol<[EMAIL PROTECTED]> wrote: I try that build, but is fails now at a earlyer point. Well, your logs show that configure succeeded, which means the fail

Re: coreutils-6.11 released

Elbert Pol <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> Elbert Pol<[EMAIL PROTECTED]> wrote: >>> I try that build, but is fails now at a earlyer point. >> >> Well, your logs show that configure succeeded, which means the >> failure is _lat

Re: Bash vs. sh

"Joel E. Denny" <[EMAIL PROTECTED]> wrote: > On Wed, 23 Apr 2008, Jim Meyering wrote: > >> > I was hoping for something more formal: all developers commit their >> > bootstrap-inner.m4sh changes to gnulib instead of to their own projects. >> >&g

Re: retaining AFS-specific nameless group IDs (PAG) in `id' and `groups'

Adam Megacz <[EMAIL PROTECTED]> wrote: > Jim Meyering <[EMAIL PROTECTED]> writes: >> Since you guys are interested in AFS, I'm hoping one of you will >> respond to the above. > > http://lists.openafs.org/pipermail/openafs-info/2008-April/029132.html Thanks

Re: [PATCH] id should not show selinux context when user is specified

Ondřej Vašík <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> Actually, I think this tiny change is enough: >> >> - if (selinux_enabled) >> + if (selinux_enabled && argc == optind) >> >> ...assuming you update the comment above that

Re: [PATCH] id should not show selinux context when user is specified

Jim Meyering <[EMAIL PROTECTED]> wrote: > +# Check with specified user, no context string should be present. > +# But if the current user is nameless, skip this part. > +test id -nu > /dev/null \ > + && id $(id -nu) | grep context= >/dev/null && fail=1 O

new snapshot available: coreutils-6.11.17-d30ac

http://meyering.net/cu/coreutils-6.11.17-d30ac.tar.lzma Changes since 6.11.11-0bc881: Jim Meyering (4): build: move a project-specific definition to cfg.mk id: do print the AFS-specific nameless group ID (called a PAG) tests: remove now-unused Makefile.am tests: update

Re: [Elbert Pol] Re: coreutils-6.11 released

Elbert Pol <[EMAIL PROTECTED]> wrote: > I have use the test version and also send the Stat.h from the test version. > --- U:\Core\lib\sys\stat.h2008-04-22 20:40:18.0 + > +++ U:\coreutils-6.11\lib\sys\stat.h 2008-04-20 10:20:02.0 + Ahh... so you did. Sorry about that.

Re: [Elbert Pol] Re: coreutils-6.11 released

Elbert Pol <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> Elbert Pol<[EMAIL PROTECTED]> wrote: >>> I have use the test version and also send the Stat.h from the test version. >>> --- U:\Core\lib\sys\stat.h 2008-04-22 20:40:18.0 + &

Re: id not showing supplementary groups

Javier Pello <[EMAIL PROTECTED]> wrote: > Hi, > > I have just downloaded and installed coreutils-6.11 and I have come > across a change in behaviour in the id program which does not seem > to be documented. Specifically, id no longer prints the supplementary > groups of the current process when inv

Re: tsort 6.9, incorrect output

Guillaume Bailey <[EMAIL PROTECTED]> wrote: > I have an example of the latest tsort producing invalid output. The 6.9 is over two years old. The latest coreutils release is coreutils-6.11. > output clearly disobeys the partial ordering 'i k a h g j', because > a' precedes both 'i' and 'k'. There

Re: "cp --no-preserve=mode" doesn't work as-expected

CJ Kucera <[EMAIL PROTECTED]> wrote: > Hello... I've run into a problem best described by a post to this list > from 2003: > >> When the destination file does not exist cp uses the permissions of the >> source file for creating the destination, as specified by POSIX. Wouldn't >> it be useful if -

Re: [Elbert Pol] Re: coreutils-6.11 released

Elbert Pol <[EMAIL PROTECTED]> wrote: > Hoi Jim, > > When i use the new rm.exe and use it with the ./configure i get all > kind of errors like : > > rm.exe: cannot remove `conftest': Is a directory > rm.exe: cannot remove `conftest.dir': Is a directory > rm.exe: FATAL: cannot enter directory `conft

Re: [Elbert Pol] Re: coreutils-6.11 released

Elbert Pol <[EMAIL PROTECTED]> wrote: ... >> Remember when you chose not to run "make -k check"? ;-) >> Well, now would be a good time to go back and do that, >> but with working tools in your PATH, of course. >> > Hoi Jim, > > As you told before this fails :( > I attach check.log Try again, but t

Re: coreutils-6.11 released

Christophe LYON <[EMAIL PROTECTED]> wrote: > On 19.04.2008 23:21, Jim Meyering wrote: >> Coreutils version 6.11 has been released. This is a stable release. > > Hello, > > My build fails on a Solaris 8 machine, using gcc-4.1.0. > When building "sort", I g

Re: "cp --no-preserve=mode" doesn't work as-expected

Matt Griswold <[EMAIL PROTECTED]> wrote: > * Jim Meyering <[EMAIL PROTECTED]> [080425 08:55]: >> Patches welcome. > > Apologies if I'm over-simplifying, I'm not familiar with the coreutils > code. This does seem to cause --no-preserve=mode to work as e

Re: [PATCH] Add new program: renice

"Bo Borgerson" <[EMAIL PROTECTED]> wrote: > This is a basic implementation of the `renice' utility: > > http://www.opengroup.org/onlinepubs/95399/utilities/renice.html Thanks, but Bob Proulx has written one already, as hinted at in TODO. I think it's nearly ready...

FYI, 11 mostly-test-related patches

[I hesitated to post so many small test-only patches all together, but it's better than not posting at all. Besides, maybe posting at all will evoke some review feedback. So here goes... ] >From 6bbbd65d895505c506105ea12e44922433e63574 Mon Sep 17 00:00:00 2001 From: Jim Meyering

Re: FYI, 11 mostly-test-related patches

"Bo Borgerson" <[EMAIL PROTECTED]> wrote: > Regarding rev. 94a2bd5b, `tests: improve perl-based tempdir handling', > I wonder if it might be worthwhile to add a PID check in the cleanup > handler for race avoidance. > > I think File::Temp does this internally as well, but it looks like > chmod_tree

Re: FYI, 11 mostly-test-related patches

Bo Borgerson <[EMAIL PROTECTED]> wrote: > Subject: [PATCH] tests: don't chmod after a failed chdir in cleanup > * tests/CuTmpdir.pm (chmod_tree): Don't chmod if chdir failed. Thanks! Applied and pushed. ___ Bug-coreutils mailing list Bug-coreutils@gnu

Re: FYI, 11 mostly-test-related patches

or directory > mv: cannot stat `tests/wc/Makefile.amt': No such file or directory > ./bootstrap: aclocal --force -I m4 ... > > I've attached a patch that addresses this. Thanks to both of you. Bo, I've applied your patch. FYI, here's one more, that will eliminate the ris

Re: FYI, 11 mostly-test-related patches

Eric Blake <[EMAIL PROTECTED]> wrote: > Jim Meyering meyering.net> writes: >> [I hesitated to post so many small test-only patches all together, >> but it's better than not posting at all. Besides, maybe posting >> at all will evoke some review feedback. S

Re: [Elbert Pol] Re: coreutils-6.11 released

Elbert Pol <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> Elbert Pol<[EMAIL PROTECTED]> wrote: >>> Hoi Jim, >>> >>> When i use the new rm.exe and use it with the ./configure i get all >>> kind of errors like : >>> >>>

chcon, runcon: --help output did not include bug reporting address

I noticed that chcon and runcon were exempted from some of the tests in misc/help-version. That exemption (probably back from when I added preliminary versions) was hiding this small defect: >From bbc0cb0f37641b1779170b3e15bd3479fb250fed Mon Sep 17 00:00:00 2001 From: Jim Meyering <

Re: Feature request - base64 Filename Safe Alphabet

Bo Borgerson <[EMAIL PROTECTED]> wrote: > Christopher Kerr wrote: >> After being burned by using `head -c6 /dev/urandom | base64` as part of a >> directory name, I realised that it would be useful if base64 had an option to >> generate URL and Filename safe encodings, as specified in RFC 3548 secti

Re: Feature request - base64 Filename Safe Alphabet

Christopher Kerr <[EMAIL PROTECTED]> wrote: > After being burned by using `head -c6 /dev/urandom | base64` as part of a > directory name, I realised that it would be useful if base64 had an option to > generate URL and Filename safe encodings, as specified in RFC 3548 section 4. > > This would make

Re: FYI, 11 mostly-test-related patches

Eric Blake <[EMAIL PROTECTED]> wrote: > Jim Meyering meyering.net> writes: >> > ./bootstrap: m4/xsize.m4 overrides ._bootmp2/m4/xsize.m4 >> > Undefined subroutine &Test::test_vector called at tests/mk-script line 44. >> > ./bootstrap: aclocal --forc

coreutils test coverage

If you're reading this list, you probably noticed that some kind souls at Stanford uncovered a surprising number of bugs in coreutils recently. Part of their analysis was coverage-related, and they produced these coverage reports: http://keeda.stanford.edu/~cristic/coreutils-dev-tests/src/ I

Re: coreutils test coverage

Bo Borgerson <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> If you're reading this list, you probably noticed that some kind >> souls at Stanford uncovered a surprising number of bugs in coreutils >> recently. Part of their analysis was coverage-related, and

Re: speed up getndelim2

Eric Blake <[EMAIL PROTECTED]> wrote: > Wow! Check out the speedup with this patch, comparing an -O2 /bin/cut > pre-patch against an unoptimized -g cut post-patch, and that's even with > running /bin/cut second so it benefits from any file system caching effects. ... > And all I did was make getnd

Re: coreutils test coverage

Bo Borgerson <[EMAIL PROTECTED]> wrote: > Daniel Dunbar wrote: >> Here is the process I use for generating those results. First, generate the >> coverage information: > > Thanks, that worked like a charm! > > I've attached a patch that puts your instructions into the HACKING file. Thanks! Applied

[PATCH] tests: avoid spurious "make check-root" failure

FYI: tests: avoid spurious "make check-root" failure * README (Running tests as root): Also set PATH in suggested "sudo" command. This avoids failure of at least tests/cp/cp-a-selinux when the default PATH does not contain /sbin. * tests/cp/cp-a-selinux: Do

[PATCH] tests: avoid a "make check-root" failure when mcstransd is running

and one more: tests: avoid a "make check-root" failure when mcstransd is running * tests/misc/chcon: Skip this test if mcstransd seems to be running. diff --git a/tests/misc/chcon b/tests/misc/chcon index 3a61c69..74248a3 100755 --- a/tests/misc/chcon +++ b/tests/misc/chcon @@ -11

Re: Feature request - base64 Filename Safe Alphabet

Bo Borgerson <[EMAIL PROTECTED]> wrote: > This is an attempt at making a base64.c that supports the context > structure for coreutils but still presents a four-argument decode > interface for gnulib. > > It doesn't address the differences in newline handling, and it's > definitely less efficient fo

Re: [PATCH] tests/cp/cp-reply: --reply only accepts valid arguments

"Brock Noland" <[EMAIL PROTECTED]> wrote: > On Wed, Apr 30, 2008 at 10:10 PM, Bob Proulx <[EMAIL PROTECTED]> wrote: >> >> Hopefully this helps, > > Yes, thank you! I will get to work... Which is preferred, one large > patch or many small patches - one for each `logical' change? Many small changes

Re: [bug #23023] cp -r use a lot of memory, feature or memory leak?

Matteo Boccafoli <[EMAIL PROTECTED]> wrote: > URL: > > Summary: cp -r use a lot of memory, feature or memory leak? ... > # 21000 dir in 1.tar.bz2 > $ cd /dev/shm > /dev/shm$ time tar -xjf 1.tar.bz2 > > real0m8.403s > user0m3.188s > s

[bug #23023] cp -r use a lot of memory, feature or memory leak?

Update of bug #23023 (project coreutils): Privacy: Private => Public ___ Reply to this item at: ___

[bug #23023] cp -r use a lot of memory, feature or memory leak?

Update of bug #23023 (project coreutils): Status:None => Confirmed ___ Follow-up Comment #2: See discussion on this thread: http://thread.gmane.org/gmane.comp.gnu.coreutils.bugs/13369

Re: Bug report: tac crash

e re_registers are in sync, but this doesn't hold when > tac makes multiple re_search calls with the registers on the stack. Hi Daniel, Thanks for the report and analysis! Here's the fix I expect to push once I've added a test. >From 8449b56e600e77e6a76f80a6cb425b90e4251319 M

Re: Bug report: tac crash

Jim Meyering <[EMAIL PROTECTED]> wrote: > Daniel Dunbar <[EMAIL PROTECTED]> wrote: >> The following crashes tac on my machine (6.10 and 6.11): >> -- >> $ echo > x; tac -r x x >> Segmentation fault >> -- >> >> The crash occurs in re_copy

Re: Bug report: tac crash

Jim Meyering <[EMAIL PROTECTED]> wrote: > Jim Meyering <[EMAIL PROTECTED]> wrote: >> Daniel Dunbar <[EMAIL PROTECTED]> wrote: >>> The following crashes tac on my machine (6.10 and 6.11): >>> -- >>> $ echo > x; tac -r x x >>> Segm

Re: Feature request - base64 Filename Safe Alphabet

Bo Borgerson <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> if you make him happy, I'll probably be happy, too ;-) > > Hi Simon, > > This is an attempt to merge the coreutils and gnulib base64 libraries. > > My goal is to preserve the gnulib interface an

Re: Feature request - base64 Filename Safe Alphabet

Bo Borgerson <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> I found "strict_newlines" to be a little unclear. >> If you use something like "ignore_newlines" instead, that's not >> only clearer to me, but with its reversed semantics it also l

Re: Bug#479544: dircolors: please eliminate duplicates before writing variable

martin f krafft <[EMAIL PROTECTED]> wrote: > Package: coreutils > Version: 6.10-6 > Severity: wishlist > File: /usr/bin/dircolors > > If I specify a filetype twice in the dircolors file, the resulting > LS_COLORS will have the entry twice: > > lapse:/% echo "EXEC 00\nEXEC 01" | dircolors - > LS

FYI, help2man change required for perl 5.10

>From 58525a9ce493cb71fde6f74e036d627c9c65bec0 Mon Sep 17 00:00:00 2001 From: Jim Meyering <[EMAIL PROTECTED]> Date: Mon, 5 May 2008 22:44:57 +0200 Subject: [PATCH] help2man: avoid failure with perl 5.10 Avoid failure that produced this diagnostic: Constant subroutine main::LC_ALL red

[PATCH] avoid problems with sign-extended "char" operand to is* functions

ch cleaner. >From a24d06f54a3a2111c3c167e30c42dc0891bb1f45 Mon Sep 17 00:00:00 2001 From: Jim Meyering <[EMAIL PROTECTED]> Date: Sat, 26 Apr 2008 09:28:48 +0200 Subject: [PATCH] avoid problems with sign-extended "char" operand to is* functions MIME-Version: 1.0 Content-Type: text

Re: FYI, help2man change required for perl 5.10

Jim Meyering <[EMAIL PROTECTED]> wrote: >>From 58525a9ce493cb71fde6f74e036d627c9c65bec0 Mon Sep 17 00:00:00 2001 > From: Jim Meyering <[EMAIL PROTECTED]> > Date: Mon, 5 May 2008 22:44:57 +0200 > Subject: [PATCH] help2man: avoid failure with perl 5.10 That wasn't

Re: [PATCH] base64: remove some unused/redundant getopt code

Bo Borgerson <[EMAIL PROTECTED]> wrote: > I noticed these when I was poking around in base64 recently. Looks like > they're vestigial. Good catch. Thank you. Applied. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/l

Re: Bug#479544: dircolors: please eliminate duplicates before writing variable

martin f krafft <[EMAIL PROTECTED]> wrote: > also sprach Jim Meyering <[EMAIL PROTECTED]> [2008.05.05.1829 +0100]: >> If no one volunteers to do this soon >> I'll put it on the TODO list. > > FWIW, this is a zsh-style way of dealing with it. It's

FYI: test-related changes

FYI, I've been factoring and cleaning up tests, moving from the mk-script-based framework to the Coreutils.pm-based ones. One interesting side effect is that this is removing *thousands* of files from the distribution tarball. On the other hand, each of the converted tests require Perl, but that's

Re: coreutils-6.11 released

Christophe LYON <[EMAIL PROTECTED]> wrote: > On 25.04.2008 21:04, Jim Meyering wrote: >> Christophe LYON <[EMAIL PROTECTED]> wrote: >>> >>> If I manually add "-lm", I get: >>> .../bin/../lib/gcc/sparc-sun-solaris2.8/4.1.0/crt1.o:(.plt+0

Re: horrible utf-8 performace in wc

Pádraig Brady <[EMAIL PROTECTED]> wrote: > Jan Engelhardt wrote: >> >> https://bugzilla.novell.com/show_bug.cgi?id=381873 >> >> Forwarding this because it is a GNU issue, not specifically a Novell one. >> I reproduced this myself with the latest coreutils from git >> (BTW: You might want to repack

Re: horrible utf-8 performace in wc

Bo Borgerson <[EMAIL PROTECTED]> wrote: > I may be misinterpreting your patch, but it seems to me that > decrementing count for zero-width characters could potentially lead to > confusion. Not all zero-width characters are combining characters, right? It looks ok to me, since there's an unconditi

Re: horrible utf-8 performace in wc

Bruno Haible <[EMAIL PROTECTED]> wrote: > 2008-05-08 Bruno Haible <[EMAIL PROTECTED]> > > Speed up "wc -m" and "wc -w" in multibyte case. > * src/wc.c: Include mbchar.h. > (wc): New variable in_shift. Use it to avoid calling mbrtowc for most > ASCII characters. Thanks! I'

Re: /usr/bin/printf: invalid universal character name

Hermann Peifer <[EMAIL PROTECTED]> wrote: > printf \u is expected to print Unicode chars. This work fine in > most cases, but some legal code points are reported as errors: values > in the ASCII range and C1 control chars, and values between > U+D800..U+DFFF > > I would say that this behavio

Re: /usr/bin/printf: invalid universal character name

Hermann Peifer <[EMAIL PROTECTED]> wrote: > Jim wrote: >> Hermann Peifer <[EMAIL PROTECTED]> wrote: >> >>> printf \u is expected to print Unicode chars. This work fine in >>> most cases, but some legal code points are reported as errors: values >>> in the ASCII range and C1 control chars, an

Re: [PATCH] md5sum+sha*sum: add option --quiet/-q to suppress OK messages

Erik Auerswald <[EMAIL PROTECTED]> wrote: > On Sun, May 04, 2008 at 06:33:45PM +0200, Erik Auerswald wrote: >> On Tue, Apr 22, 2008 at 07:10:58PM +0200, Jim Meyering wrote: >> > Erik Auerswald <[EMAIL PROTECTED]> wrote: >> > > On Tue, Apr 22, 20

Re: [PATCH] md5sum+sha*sum: add option --quiet/-q to suppress OK messages

Erik Auerswald <[EMAIL PROTECTED]> wrote: > On Tue, May 13, 2008 at 03:12:57PM +0200, Jim Meyering wrote: >> Erik Auerswald <[EMAIL PROTECTED]> wrote: >> > The copyright assignment process with the FSF is completed, find the >> > patch against current HE

Re: /usr/bin/printf: invalid universal character name

Hermann Peifer <[EMAIL PROTECTED]> wrote: > Jim, > > Is this case closed now and we simply agree that, for whatever > (potentially good) reason: printf "\u" only prints 3 characters > (DOLLAR SIGN, COMMERCIAL AT and GRAVE ACCENT) in the range > \u..\u009f It's not closed. I'm hoping that s

Re: /usr/bin/printf: invalid universal character name

Bruno Haible <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> Paul Eggert added this feature 8 years ago > > Well, all honours to Paul, but this feature I did submit to you on 2000-02-02. Oh! Sorry to misattribute that. I looked at the wrong ChangeLog entry. >>

Re: /usr/bin/printf: invalid universal character name

Jim Meyering <[EMAIL PROTECTED]> wrote: > Hermann Peifer <[EMAIL PROTECTED]> wrote: >> Is this case closed now and we simply agree that, for whatever >> (potentially good) reason: printf "\u" only prints 3 characters >> (DOLLAR SIGN, COMMERCIAL

Re: /usr/bin/printf: invalid universal character name

"Hermann Peifer" <[EMAIL PROTECTED]> wrote: > Jim Meyering <[EMAIL PROTECTED]> wrote: >> Bruno Haible <[EMAIL PROTECTED]> wrote: >> > Jim Meyering wrote: >> >> Paul Eggert added this feature 8 years ago >> > >> > Well

[PATCH] make HACKING slightly more generic

FYI, just pushed: make HACKING slightly more generic * HACKING: remove some uses of "coreutils" Point to git's own SubmittingPatches URL. diff --git a/HACKING b/HACKING index c33bdd3..3b7b408 100644 --- a/HACKING +++ b/HACKING @@ -187,7 +187,7 @@ It's easy to adjust: gi

new snapshot available: coreutils-6.11.85-c4a95

: adjust API so it's compatible with gnulib's base64: remove some unused/redundant getopt code Bruno Haible (2): Speed up "wc -m" and "wc -w" in multibyte case. doc: some Unicode characters cannot be specified via \u or \U Jim Meyering (59): test

Re: [PATCH] Clarify field delimiter description in uniq --help output

Pádraig Brady <[EMAIL PROTECTED]> wrote: >>From 9228e10c4c68ffd585bbb6e5fd7efbab6f6c5f97 Mon Sep 17 00:00:00 2001 > From: =?utf-8?q?P=C3=A1draig=20Brady?= <[EMAIL PROTECTED]> > Date: Mon, 19 May 2008 07:54:07 +0100 > Subject: [PATCH] Clarify field delimiter description in uniq --help output > > * s

Re: [PATCH] Clarify field delimiter description in uniq --help output

Pádraig Brady <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >>> Hi Pádraig, >>> >>> Thanks! >>> Your summary is right, but the --help change is slightly >>> inaccurate, since "blank" can mean more than just SPC or TAB. > > Y

Re: should GNU install call matchpathcon by default?

tem 97% cpu 0.391 total # matchpathcon code in use: $ touch k; time ( for i in $(seq 200); do; ./ginstall k /usr/tmp/k ;done ) 7.19s user 1.62s system 99% cpu 8.840 total >From a089634c855312a28f2ff3c2e7c08df5d030e2f5 Mon Sep 17 00:00:00 2001 From: Jim Meyering <[EMAIL PROTECTED]> Da

Re: should GNU install call matchpathcon by default?

"Eric Paris" <[EMAIL PROTECTED]> wrote: > On Tue, May 20, 2008 at 12:13 PM, Jim Meyering <[EMAIL PROTECTED]> wrote: >> Stephen Smalley <[EMAIL PROTECTED]> wrote: >> ... >>> This issue came up recently again, see: >>> https://bugzilla.

Re: should GNU install call matchpathcon by default?

Ondrej Vasik <[EMAIL PROTECTED]> wrote: > Jim Meyering meyering.net> writes: >> In the multi-file case, the pre-patch performance penalty for enabling >> the ifdef'd-out code would range from probably-immeasurable (for just >> 2 or 3 files) to infinite, with e

Re: coreutils-6.11-1 in release-2 area

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Corinna Vinschen on 5/22/2008 6:30 AM: > |>> Meanwhile, it IS a bit annoying that Posix 200x decided not to standardize > |>> utimensat(fd,NULL,times,flag) as changing the times on fd rather than > |>> treating fd as the directory starting point;

[OT] recommended reading: usenix malicious hardware paper

Here's an awe-inspiring paper. A colleague's summary was apt: "we're all doomed" ;-) http://www.usenix.org/event/leet08/tech/full_papers/king/king_html/ You will view older hardware with more respect. ___ Bug-coreutils mailing list Bug-coreutils@gn

new snapshot available: coreutils-6.11.104-00a30

utils-ss.tar.lzma.sig aka http://meyering.net/cu/coreutils-6.11.104-00a30.tar.gz http://meyering.net/cu/coreutils-6.11.104-00a30.tar.lzma Changes since 6.11.85-c4a95: Jim Meyering (18): use gnulib's base64 module, now that it's sync'd to match this one install: avoid

Re: utimens and non-standardized futimesat

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Eric Blake on 5/22/2008 6:51 AM: > | According to Jim Meyering on 5/22/2008 6:42 AM: > | |> |> No need to refer the dir by name: > | |> |> > | |> |> futimens (dirfd. timespec); > | |> | > | |>

Re: du v5.93: traverses subdirectories although --separate-dirs and --summarize are set?

"Volker Badziong" <[EMAIL PROTECTED]> wrote: > I do not understand why this is necessary if the results from subdirectories > are not taken into account? Or asked the other way: What information from the > traversal process is taken into the total sum? > > E.g. look at the following. du yields al

Re: Bug#483554: coreutils: "info chcon" gives the man page instead of the full documentation

Vincent Lefevre <[EMAIL PROTECTED]> wrote: > Package: coreutils > Version: 6.10-6 > Severity: normal > > The chcon(1) man page says: > > SEE ALSO >The full documentation for chcon is maintained as a Texinfo >manual. If the info and chcon programs are properly installed >

Re: coreutils-6.11.104-00a30 test results

Bruno Haible <[EMAIL PROTECTED]> wrote: > Test results on MacOS X 10.5.2 and MacOS X 10.3.9: > > - On MacOS X 10.5.2: All coreutils tests pass, and all gnulib tests pass! > On this platform, perl 5.8.8 is used. > > This is an improvement over version 6.11. Why not mention it in NEWS: > "On MacOS X

Re: coreutils-6.11.104-00a30 test results

e. I've been tempted to exclude it before, too... Do you know what it was trying to do when hung? I know it tries to connect to these systems: #define HOST1 "www.gnu.org" #define HOST2 "www.ibm.com" #define HOST3 "microsoft.com" #define HOST4 "google

FYI

utils.bugs/13652 commit eb4b2d462ea462547269b6380c6074e3ffcb60cf Author: Jim Meyering <[EMAIL PROTECTED]> Date: Fri May 30 14:14:43 2008 +0200 configure.ac: remove explicit use of AB_INIT * configure.ac: Don't invoke AB_INIT directly, now that it's done automatically via gl_INIT. diff -

Re: base64: fix typos in comment

Simon Josefsson <[EMAIL PROTECTED]> wrote: > Hi! I looked over the base64 tool a bit, and found two minor issues. > Subject: [PATCH] Improve comments. ... Thanks! Applied. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mai

coreutils-6.12 released

Coreutils version 6.12 has been released. This is a stable, bug-fix release. For a summary of changes and contributors, see: http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=shortlog;h=v6.12 or run this command from a git-cloned coreutils directory: git shortlog v6.11..v6.12 To summarize the g

Re: coreutils-6.12 released

Erik Auerswald <[EMAIL PROTECTED]> wrote: > On Sun, Jun 01, 2008 at 12:15:02PM +0200, Jim Meyering wrote: >> Coreutils version 6.12 has been released. >> This is a stable, bug-fix release. > > 'make syntax-check' fails using a fresh clone of the git repo. A &g

Re: [PATCH] md5sum+sha*sum: add option --quiet/-q to suppress OK messages

Erik Auerswald <[EMAIL PROTECTED]> wrote: > And here it is... (attached). Thanks. Here are some minor changes I expect to "amend" into your patch. They alphabetize lists, tweak wording and correct a comment. Plus, in NEWS (as in ChangeLog/commit log), it's good to list all program names explicitly

Re: base64: fix typos in comment

Simon Josefsson <[EMAIL PROTECTED]> wrote: > That was quick, thanks. I went over the documentation as well. Pushed, too. I added a "doc:" prefix on the summary line, and the usual "* filename (section)" ChangeLog stuff, though I'm not sure it's worth doing that for documentation. __

<    1   2   3   4   5   6   7   8   9   10   >