On Thu, Dec 20, 2018 at 9:30 PM Jim Meyering wrote:
> I've attached the patch I expect to push in less than 30 minutes, in
> case someone wants to review or test quickly.
> I've also created a snapshot here:
>
> sed snapshot:
> https://meyering.net/sed/sed-ss.tar.xz 1.3 MB
> https://meyer
I've attached the patch I expect to push in less than 30 minutes, in
case someone wants to review or test quickly.
I've also created a snapshot here:
sed snapshot:
https://meyering.net/sed/sed-ss.tar.xz 1.3 MB
https://meyering.net/sed/sed-ss.tar.xz.sig
https://meyering.net/sed/sed-4.6.2
On Thu, Dec 20, 2018 at 9:13 PM wrote:
> > I expect to revert the mentioned mentioned gnulib commits, and then to
> > make new releases of both grep and sed.
>
> Please add a test case ...
You should know me better by now.
I didn't mention the required NEWS update either.
Jim Meyering wrote:
> On Thu, Dec 20, 2018 at 2:49 PM Jan Palus wrote:
> > I've just happened to notice a difference in behavior between sed 4.5 and
> > 4.6
> > when building VirtualBox. It seems to be locale dependent:
> >
> > $ echo 'foo(bar '|LC_ALL=C sed -e 's/\([^*] *\)\bbar\b/\1foo */g'
>
On Thu, Dec 20, 2018 at 2:49 PM Jan Palus wrote:
> I've just happened to notice a difference in behavior between sed 4.5 and 4.6
> when building VirtualBox. It seems to be locale dependent:
>
> $ echo 'foo(bar '|LC_ALL=C sed -e 's/\([^*] *\)\bbar\b/\1foo */g'
> foo(bar
>
> $ echo 'foo(bar '|LC_ALL
Hi Bruno,
Bruno Haible wrote on Thu, Dec 20, 2018 at 09:55:25PM +0100:
> I have now submitted a request to add such a method to POSIX. Here:
> http://austingroupbugs.net/view.php?id=1220
Yes, i had seen that request.
> I used OpenBSD 6.2 as an example in there, not to bash OpenBSD,
Nothing is
* lib/version-etc.c (version_etc_arn): If no authors are given,
omit authorship info instead of dumping core.
No need to include stdlib.h now.
---
ChangeLog | 6 ++
lib/version-etc.c | 6 +++---
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index
Hi Ingo,
Thanks for your thoughts. I appreciate that you give true consideration
to arguments.
> But i guess discussing such considerations in detail would be
> off-topic on this mailing list
We can stay on this mailing list. I'm not going to go deep into OpenBSD
specific system design arguments
On Thu, Dec 13, 2018 at 06:34:51PM +0300, Roman Bolshakov wrote:
> Hello,
>
> There was an issue with syntax-check on FreeBSD reported a few years
> ago:
> https://www.redhat.com/archives/libvir-list/2015-August/msg00758.html
> http://lists.gnu.org/archive/html/bug-gnulib/2015-08/msg00019.html
>
Hi Arnold,
> > >2) change those gnulib modules that don't behave well with beyond-BMP
> > > characters on Windows and AIX to use char32_t instead of wchar_t.
> ...
> I assume you'll make parallel changes in dfa.c at the same time?
If dfa.c does have bugs w.r.t. beyond-BMP characters, ye
Hi Bruno,
On Thu, 20 Dec 2018, Bruno Haible wrote:
> > Such convention concerning the meaning of EOPNOTSUPP was also stated
> > in The Open Group Base Specifications Issue 6
> > IEEE Std 1003.1, 2004 Edition
> > (http://pubs.opengroup.org/onlinepubs/009604599/functions/lchown.html);
> > however,
11 matches
Mail list logo