Tom Lane wrote:
> Alvaro Herrera 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
Alvaro Herrera 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 hig
Tom Lane wrote:
> Magnus Hagander 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
Tom Lane wrote:
> Magnus Hagander 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
Magnus Hagander 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 mes
I have cleaned up a couple of badly broken encodings in cvs commit
messages in:
src/backend/utils/error/Attic/exc.c,v
per discussion with Alvaro, by simply editing the RCS file directly in
the cvs repository. Only the commit message was changed (broken
character removed)
Should have no effect.
