Re: [COMMITTERS] pgsql: /home/peter/commit-msg
От | Heikki Linnakangas |
---|---|
Тема | Re: [COMMITTERS] pgsql: /home/peter/commit-msg |
Дата | |
Msg-id | 4B06F188.3090308@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: /home/peter/commit-msg (Kris Jurka <books@ejurka.com>) |
Ответы |
Re: [COMMITTERS] pgsql: /home/peter/commit-msg
Re: [COMMITTERS] pgsql: /home/peter/commit-msg |
Список | pgsql-hackers |
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. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: