| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, David Fetter <david(at)fetter(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] pgsql: /home/peter/commit-msg |
| Date: | 2009-11-20 08:11:55 |
| Message-ID: | alpine.BSO.2.00.0911200302260.18540@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-11-20 19:44:08 | Re: [HACKERS] pgsql: /home/peter/commit-msg |
| Previous Message | Magnus Hagander | 2009-11-20 01:28:18 | pgsql: Revert backpatch of inheritable-ACE patch for Win32, since it |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Pye | 2009-11-20 08:20:04 | Re: Python 3.1 support |
| Previous Message | Greg Stark | 2009-11-20 07:47:50 | Re: enable-thread-safety defaults? |