Re: clcommit

[Ralf Wildenhues]

* Gary V. Vaughan wrote on Tue, Feb 01, 2005 at 01:08:48PM CET:
> Ralf Wildenhues wrote:
> > Looks like clcommit.m4sh eats backspaces, hehe.
> 
> Err... back _slashes_, right?   I wondered why it took me two
> reads to understand this ;-)

Darn, it was too late last night.  Yes, backslashes.  Sorry.

> > Proposed, untested patch below (I don't care too much if they get
> > eaten, so if your shell does not do `read -r', then so be it).
> 
> Good catch!  Looks okay from here.

Well, I thought clcommit was maintained elsewhere, and I didn't like the
idea of changing without notifying upstream.  But since you say so..

Committed to HEAD and branch-2-0.  ChangeLog entry below (yes, the entry
contains a backslash on purpose).  No update of copyright year because
of mostly trivial change.

> If it passes the testsuite, please add a ChangeLog and commit.

Do you have the impression I need to use `make check' more often? :)

Regards,
Ralf

        * clcommit.m4sh: Test whether the shell understands `read -r'.  Use as
        `$read_r' if available, so `\' is preserved in commit notices.