[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ensure that generated files are read-only

From: Ralf Wildenhues
Subject: Re: ensure that generated files are read-only
Date: Thu, 7 Sep 2006 16:27:56 +0200
User-agent: Mutt/1.5.13 (2006-09-01)

* Bruce Korb wrote on Thu, Sep 07, 2006 at 04:00:32PM CEST:
> No hidden commands without a good reason for hiding the command.

FWIW, I agree with this notion.  More generally, I think that if you
want to make "nicer make output", then I prefer a Linux style that I
(with my bug report reader hat on) can recognize and dismiss right away,
rather than having just part of the commands and leaving me with lots
of guessing.

While we're at this topic, I tried `./configure -C -q' for less output,
and saw this stray line in a coreutils build.  Any reasons against this,
Jim, similar to getaddrinfo.m4?


        * fsusage.m4 (gl_FILE_SYSTEM_USAGE): Don't use plain echo.

Index: m4/fsusage.m4
RCS file: /cvsroot/gnulib/gnulib/m4/fsusage.m4,v
retrieving revision 1.27
diff -u -r1.27 fsusage.m4
--- m4/fsusage.m4       1 Sep 2006 19:49:22 -0000       1.27
+++ m4/fsusage.m4       7 Sep 2006 14:22:57 -0000
@@ -1,4 +1,4 @@
-#serial 20
+#serial 21
 # Obtaining file system usage information.
 # Copyright (C) 1997, 1998, 2000, 2001, 2003, 2004, 2005, 2006 Free Software
@@ -35,7 +35,7 @@
-echo "checking how to get file system space usage..."
+AC_MSG_CHECKING([how to get file system space usage])
 # Perform only the link test since it seems there are no variants of the

reply via email to

[Prev in Thread] Current Thread [Next in Thread]