Re: Git migration

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: Git migration
Дата
Msg-id 516EA7CC.2030004@vmware.com
обсуждение исходный текст
Ответ на Re: Git migration  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: Git migration  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Список pgsql-odbc
On 16.04.2013 17:03, Alvaro Herrera wrote:
> Heikki Linnakangas wrote:
>> Please take a look at the updated repository at
>> https://github.com/hlinnaka/psqlodbc-migration.
>
> Looks pretty good, yes.
>
> There are a couple of bogus chars in these commits:

Thanks for checking!

> commit bc5d1a6dfa0a2cb9c530347e46a46186dd45fac8
> Author: Dave Page<dpage@pgadmin.org>
> Date:   Thu Dec 8 09:11:28 2005 +0000

This seems to be in Win1250 encoding. Fixed.

> commit ab41b413019311f60decefa46d36791704502d50
> Author: Dave Page<dpage@pgadmin.org>
> Date:   Fri Apr 9 18:13:12 2004 +0000

The problematic string in the commit message is "Cyrille Ch?p?lov". The
question marks are there in the CVS ,v file already, so the damage to
the characters was already when the CVS commit was made. I'm inclined to
leave it as it is, to be as close to the CVS repository as possible. Or
we could fix that commit message manually; they are supposed to be "é"
characters.

> commit f6630a50869c33042abbd4491e1ac5b178208ece
> Author: Hiroshi Inoue<inoue@tpf.co.jp>
> Date:   Wed Nov 12 10:15:21 2003 +0000

There is a byte 0x81 at the beginning of line, on some lines of the
commit message. I don't understand how that happened, but I'll convert
them to spaces.

I ran the migration again, with fixes for the two of those issues, and
pushed the result to the github repository again. Attached are the
scripts I used, if someone is interested. They're a bit rough, but
doesn't matter as this is a one-off thing..

- Heikki

Вложения

В списке pgsql-odbc по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Git migration
Следующее
От: Marco Gaiarin
Дата:
Сообщение: [OT] Mixing 32/64 bit...