Robert Haas wrote:
> On Thu, Sep 2, 2010 at 8:13 AM, Michael Haggerty <mhagger(at)alum(dot)mit(dot)edu> wrote:
>> What weirdness, exactly, are you discussing now? I've lost track of
>> which problem(s) are still unresolved.
> Lots of commits that look like this:
> commit c50da22b6050e0bdd5e2ef97541d91aa1d2e63fb
> Author: PostgreSQL Daemon <webmaster(at)postgresql(dot)org>
> Date: Sat Dec 2 08:36:42 2006 +0000
> This commit was manufactured by cvs2svn to create branch 'REL8_2_STABLE'.
> Sprout from master 2006-12-02 08:36:41 UTC PostgreSQL Daemon
> <webmaster(at)postgresql(dot)org> ''
I addressed that problem in this email:
Summary: it is caused by a known weakness in cvs2svn's
branch-parent-choosing code that would be difficult to solve.
But it just occurred to me--the script contrib/git-move-refs.py is
supposed to fix problems like this. Have you run this script against
your git repository? (Caveat: I am not very familiar with the script,
which was contributed by a user. Please check the results carefully and
let us know how it works for you.)
In response to
pgsql-hackers by date
|Next:||From: Dimitri Fontaine||Date: 2010-09-02 13:51:18|
|Subject: Re: Synchronous replication - patch status inquiry|
|Previous:||From: Tom Lane||Date: 2010-09-02 13:12:33|
|Subject: Re: compiling with RELCACHE_FORCE_RELEASE doesn't pass regression |