Re: encoding cleanups in cvs repo

Alvaro Herrera <alvherre@commandprompt.com> writes:
> Tom Lane wrote:
>> Out of curiosity ... what problems exactly?  I just looked through my
>> last complete dump of CVS log history and didn't see anything funny
>> in the messages for exc.c ...

> It's rev 1.7 of that file -- it had a ^E and a ^L.

Ah, I was looking for high-bit-set characters.  Yeah, I see those.
The backtick is clearly the right thing if you compare to the adjacent
commit message for another branch.
        regards, tom lane