Hello,
* Paul Eggert wrote on Thu, Apr 06, 2006 at 04:31:35AM CEST:
> [EMAIL PROTECTED] (Eric Blake) writes:
>
> > Do we want a consistent when doing a regex for both characters,
> > where order doesn't matter; which is different than doing a literal
> > like IFS where order does matter?
>
> Yes we do. We want tab-space. That's the point of the maintainer rule.
>
> I checked in the obvious fix.
The other instances can have this obvious fix, too. Checked in as
below.
Thanks for proof-reading my patches!
Cheers,
Ralf
* lib/autoconf/status.m4: More replacements to
<tab><space> where this makes sense.
Index: lib/autoconf/status.m4
===================================================================
RCS file: /cvsroot/autoconf/autoconf/lib/autoconf/status.m4,v
retrieving revision 1.92
diff -u -r1.92 status.m4
--- lib/autoconf/status.m4 6 Apr 2006 02:28:56 -0000 1.92
+++ lib/autoconf/status.m4 6 Apr 2006 17:26:23 -0000
@@ -363,7 +363,7 @@
m4_define([_AC_SED_CMD_NUM], m4_eval(_AC_SED_CMD_NUM + 3))dnl
m4_define([_AC_SED_FRAG],
m4_defn([_AC_SED_FRAG])dnl
-[/^[ @&t@ [EMAIL PROTECTED]@[ @&t@ ]*$/{
+[/^[ [EMAIL PROTECTED]@[ ]*$/{
r $]_AC_Var[
d
}
@@ -641,8 +641,8 @@
dnl Quote, for the `[ ]' and `define'.
echo [' # First, check the format of the line:
cat >"$tmp/defines.sed" <<CEOF
-/^[ ]*#[ ]*undef[ ][ ]*$ac_word_regexp[ @&t@ ]*$/b
def
-/^[ ]*#[ ]*define[ ][ ]*$ac_word_regexp[( @&t@ ]/b def
+/^[ ]*#[ ]*undef[ ][ ]*$ac_word_regexp[ ]*$/b def
+/^[ ]*#[ ]*define[ ][ ]*$ac_word_regexp[( ]/b def
b
:def'] >>$CONFIG_STATUS
sed ${ac_max_sed_lines}q conftest.defines >>$CONFIG_STATUS
