Re: [COMMITTERS] pgsql: /home/peter/commit-msg
От | Robert Haas |
---|---|
Тема | Re: [COMMITTERS] pgsql: /home/peter/commit-msg |
Дата | |
Msg-id | 603c8f070911201158o48349ef5uae78c9bae0d59b31@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: /home/peter/commit-msg (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Список | pgsql-hackers |
On Fri, Nov 20, 2009 at 2:44 PM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > Kris Jurka wrote: >> On Fri, 20 Nov 2009, Magnus Hagander wrote: >> >>> I've cleaned up the git repo, and re-enabled the mirror script. From >>> what I can tell it works fine. In theory you will need to use force >>> mode if you pulled the broken commit that was removed (the one with >>> the wrong message), but it seems this is not necessarily required. >> >> Just to clarify here, what was the point of stopping the sync script? >> Unless the sync was stopped prior to the modified commit there's no >> difference for an end user here. If they pulled the modified commit >> they've got a semi-broken repo. All that's happened is that they >> weren't able to pull newer updates as well which seems like a net loss. > > We figured it's easier to backtrack if there's no more commits on top of > the modified one. Not sure how true it really was. FWIW, I had good luck with "git rebase origin/master". ...Robert
В списке pgsql-hackers по дате отправления: