[PATCH] maint: move definitions from maint.mk to dist-check.mk

This goes with today's gnulib change: From 02919661750c535e67fd204345e2ac4982c70887 Mon Sep 17 00:00:00 2001 From: Jim Meyering meyer...@redhat.com Date: Sun, 13 Dec 2009 10:35:49 +0100 Subject: [PATCH] maint: move definitions from maint.mk to dist-check.mk * dist-check.mk (null_AM_MAKEFLAGS):

Re: tail + inotify over nfs

Pádraig Brady wrote: I've just noticed that `tail -f` will not work over NFS as changes on the remote system will not go through the local VFS and so will not be noticed by inotify. Ouch. Good catch. Testing with `tail -s.1 ---disable-inotify` does get the changes noticed, albeit after a

[PATCH] tests: make the taint-distcheck rule easier to share with other projects

This is useful for parted, since it shares this file, yet cannot pass the taint-distcheck test due to the fact that it uses libtool. From 6ee02e3d8301eb7fb58b374c72b41c52836a104d Mon Sep 17 00:00:00 2001 From: Jim Meyering meyer...@redhat.com Date: Wed, 9 Dec 2009 10:26:21 +0100 Subject: [PATCH]

Re: tail + inotify over nfs

Jim Meyering j...@meyering.net writes: Pádraig Brady wrote: Testing with `tail -s.1 ---disable-inotify` does get the changes noticed, albeit after a delay of 3s on my setup. Odd that it would take so long. Probably due to caching? Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key

Re: tail + inotify over nfs

Hello, Jim Meyering j...@meyering.net writes: Pádraig Brady wrote: I've just noticed that `tail -f` will not work over NFS as changes on the remote system will not go through the local VFS and so will not be noticed by inotify. So what to do? I suppose we could statfs(filename) Yes, I

Re: tail + inotify over nfs

Giuseppe Scrivano wrote: Hello, Jim Meyering j...@meyering.net writes: Pádraig Brady wrote: I've just noticed that `tail -f` will not work over NFS as changes on the remote system will not go through the local VFS and so will not be noticed by inotify. So what to do? I suppose we could

[PATCH] rm: Correct brace indention of enum interactive_type

From: David Soria Parra d...@php.net * src/rm.c: Correct brace indention --- src/rm.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/rm.c b/src/rm.c index 2b62e5b..7ae502c 100644 --- a/src/rm.c +++ b/src/rm.c @@ -55,11 +55,11 @@ enum }; enum interactive_type

[PATCH] base64: use the HELP and VERSION macros instead of the hard coded text.

From d94e2570f936dc44f719177fd81abe8311955598 Mon Sep 17 00:00:00 2001 From: Thiago Farina tfrans...@gmail.com Date: Sun, 13 Dec 2009 14:27:59 -0500 Subject: [PATCH] base64: use the HELP and VERSION macros instead of the hard coded text. * src/base64: Use HELP_OPTION_DESCRIPTION and

[PATCH] rm: Proper indenting of enum braces

From: David Soria Parra d...@php.net * src/rm.c: Reindent interactive_type enum braces --- src/rm.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/rm.c b/src/rm.c index 2b62e5b..7ae502c 100644 --- a/src/rm.c +++ b/src/rm.c @@ -55,11 +55,11 @@ enum }; enum

Re: [PATCH] base64: use the HELP and VERSION macros instead of the hard coded text.

Thiago Farina wrote: Subject: [PATCH] base64: use the HELP and VERSION macros instead of the hard coded text. * src/base64: Use HELP_OPTION_DESCRIPTION and VERSION_OPTION_DESCRIPTION macros instead of the hard coded text. Thanks. I adjusted the log message and pushed that.