From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | pgsql-www(at)postgresql(dot)org |
Subject: | PostgreSQL GIT mirror status |
Date: | 2008-12-30 20:18:53 |
Message-ID: | 495A822D.2040804@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
The PostgreSQL GIT mirror at git.postgresql.org/git/postgresql.git was
screwed up on Dec 13th. All the history up to that date was duplicated
four times, and strange "fixup" commits appeared in back-branches. In
addition, there was the old issue that back-branches were not being updated.
Both issues have now been fixed. The repository was "reset" to the
situation before the screwup on Dec 13th, and all the patches after that
were reapplied.
This means that if you have a clone that has been updated (pulled) since
that date, the next time you issue fetch or pull, it will fail,
complaining about "non fast-forward" updates. You will need to use the
--force option to force it.
If you have any local branches in your repository, you will need to
rebase them over the new head. With something like:
git-rebase origin/master
Let's hope that the script can now keep the mirror up-to-date without
manual intervention. Let me know if there's problems.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2008-12-30 22:00:39 | Re: PostgreSQL GIT mirror status |
Previous Message | Magnus Hagander | 2008-12-30 19:51:26 | Re: Need idea for a web framework for NLS site |