The Git repo certainly is an "incremental" update.
If you ever see a "rewind" (non-fastforward) of the the repo.or.cz
PostgreSQL repo, please let me know...
a.
* Florian Pflug <fgp.phlo.org@gmail.com> [080208 07:50]:
> I've tried with both the SVN and the GIT mirror. Things worked well
> initialled, but in *both* cases pulling changes from the mirror stopped
> working after a few weeks or so. It seems that both of these mirrors
> create the SVN/GIT repo from scratch every time they are updated,
> instead of incrementally pulling the changes from CVS. Since the mapping
> of CVS updates to changesets is based on heuristics, the mapping can
> change for recent commits upon recreation of the mirror. This confuses
> both the GIT and the SVN client, and "svn update" (or "git pull") stops
> working :-(.
>
> For GIT, I've found a workaround - I've hacked together a script which
> uses git-cherry and git-cherry-pick to find changesets on the GIT mirror
> which are not in my local tree.
>
> Is there any chance that these mirrors can be updated in a way that
> doesn't "change the past"?
--
Aidan Van Dyk Create like a god,
aidan@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
