Re: [HACKERS] [COMMITTERS] pgsql: Update copyright for 2017

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: [HACKERS] [COMMITTERS] pgsql: Update copyright for 2017
Дата
Msg-id CABUevEwvAUHJpwgQedqhwXg+XJgzANYqfRS5-wOUDa3KeK8-cw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] [COMMITTERS] pgsql: Update copyright for 2017  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: [HACKERS] [COMMITTERS] pgsql: Update copyright for 2017  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers


On Tue, Jan 3, 2017 at 7:33 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Magnus Hagander <magnus@hagander.net> writes:
>> Ok. Now let's wait for the fallout from the reset. This is an interesting
>> experiment, we'll find out how many people are annoyed by a reset :-).

> I bet a number of buildfarm machines will dislike it :(

Early returns don't look good, eg on termite

        From git://git.postgresql.org/git/postgresql
           7e3ae54..83a25a5  REL9_2_STABLE -> REL9_2_STABLE
           7e3ae54..83a25a5  github/REL9_2_STABLE -> github/REL9_2_STABLE
        From /home/pgbuildfarm/buildroot-termite/pgmirror
         + 19371e1...83a25a5 REL9_2_STABLE -> origin/REL9_2_STABLE  (forced update)

        *** Please tell me who you are.

        Run

          git config --global user.email "you@example.com"
          git config --global user.name "Your Name"

        to set your account's default identity.
        Omit --global to set the identity only in this repository.

        fatal: empty ident  <pgbuildfarm@ajivana.pg.osuosl.org> not allowed

Somehow the reset is clobbering local configuration on some members?

I doubt that. I think that was probably never configured, it just didn't show up when everything was working.

I don't know what the buildfarm run, but perhaps it's trying to inject a merge commit there or something, and that's why it's failing on not having a name?

It *should* certainly not be required to have a name in order to pull.

 
We should advise buildfarm owners how to fix that.


I'm guessing the solution is to reset the 9.2 branch to a point prior to the commit and then pull again? Or wouldn't just a rebase work? 


--

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] [COMMITTERS] pgsql: Update copyright for 2017
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] ALTER TABLE .. ALTER COLUMN .. ERROR: attribute .. haswrong type