Re: encoding cleanups in cvs repo - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: encoding cleanups in cvs repo
Date
Msg-id 4950A7C4.4030908@hagander.net
Whole thread Raw
In response to Re: encoding cleanups in cvs repo  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>> I have cleaned up a couple of badly broken encodings in cvs commit
>> messages in:
> 
>> src/backend/utils/error/Attic/exc.c,v
> 
> 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 ...

***************
*** 1337,1344 **** log @Avoiding cc1: warnings being treated as errors
! exc.c: In function ^ExcRaise':
! exc.c:186: warning: passing arg 1 of ^Longjmp' from incompatible
pointer type gmake[3]: *** [exc.o] Error 1
 Now we have:
--- 1337,1344 ---- log @Avoiding cc1: warnings being treated as errors
! exc.c: In function 'ExcRaise':
! exc.c:186: warning: passing arg 1 of 'Longjmp' from incompatible
pointer type gmake[3]: *** [exc.o] Error 1



That's the output from diff, which also doesn't properly recognise the
character, but it should give you a pointer where it is. (It's not just
the ^ character, that's what diff shows me for something else, obviously)

I think it's a "backtick" in some encoding.

//Magnus



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Hot standby and b-tree killed items
Next
From: "Fujii Masao"
Date:
Subject: Re: Sync Rep: First Thoughts on Code