Re: PostgreSQL 8.4 development plan

Поиск
Список
Период
Сортировка
От Florian Pflug
Тема Re: PostgreSQL 8.4 development plan
Дата
Msg-id 47AC4F44.6090208@gmail.com
обсуждение исходный текст
Ответ на Re: PostgreSQL 8.4 development plan  (Peter Eisentraut <peter_e@gmx.net>)
Ответы Re: PostgreSQL 8.4 development plan  (Aidan Van Dyk <aidan@highrise.ca>)
Re: PostgreSQL 8.4 development plan  (Alvaro Herrera <alvherre@commandprompt.com>)
Список pgsql-hackers
Peter Eisentraut wrote:
> Am Freitag, 8. Februar 2008 schrieb Brendan Jurd:
>> In particular, if the git repos were officially supported, and best
>> practises for use with Postgres documented, I think a lot more hackers
>> would be comfortable using git to do their work, which is good for
>> collaboration (as mentioned by Greg Stark and Heikki upthread).
> 
> Well, I didn't want to announce anything before anything existed, but this is 
> precisely what is being worked on.  Watch for an announcement in this forum.

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"?

regards, Florian Pflug




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: PostgreSQL 8.4 development plan
Следующее
От: Aidan Van Dyk
Дата:
Сообщение: Re: PostgreSQL 8.4 development plan