Re: carriage return line endings vs. literal ^M in status.m4

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Jim Meyering on 4/5/2008 6:54 AM:
|>
|> then it would make a difference.  The original aim was that users should
|> be able to substitute any characters they like (except for \0).  And the
|> above is not so unlikely if the configure script itself happens to be
|> converted to w32 text mode.
|
| Good to know I wasn't preserving that code for nothing ;-)
| I'll add a comment to that effect.
|

I'd like to see the revised patch, but at this point, I think the concept
of the patch seems minimally invasive enough: it helps out Elbert's case,
without changing the behavior on previously tested platforms.  So I'm
leaning towards allowing it prior to releasing 2.62.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkf3eS0ACgkQ84KuGfSFAYDSBwCggfOaSY7TVfaCuUEYbF3pums/
mQ0An2gxN4cLfyhGCH9hrqr6InBoHgjM
=DpPj
-----END PGP SIGNATURE-----