From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Max Bowsher <maxb(at)f2s(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Michael Haggerty <mhagger(at)alum(dot)mit(dot)edu>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: git: uh-oh |
Date: | 2010-08-20 20:39:32 |
Message-ID: | AANLkTikUpy6-jx9XAjY-F9DXA+EDjHwb4B_T9kYvSMGM@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Aug 20, 2010 at 4:27 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Max Bowsher <maxb(at)f2s(dot)com> writes:
>> On 20/08/10 21:08, Tom Lane wrote:
>>> I'm still confused as to why this results in such massive weirdness in
>>> the generated git history, though. If it simply caused an extra commit
>>> that adds the new file slightly earlier than the commit we think of as
>>> adding the file, I wouldn't be complaining.
>
>> Isn't this what's happening?
>
> Uh, no, the excitement is about this:
> http://git.postgresql.org/gitweb?p=postgresql-migration.git;a=shortlog;h=refs/tags/REL8_3_10
>
> There are a whole lot of commits listed there that have nothing to do
> with anything that ever happened on the 8.3 branch.
Tom,
The problem you are looking at here has been fixed. We are looking at
a different problem now. See:
http://git.postgresql.org/gitweb?p=git-migration-test.git;a=summary
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Aidan Van Dyk | 2010-08-20 20:57:25 | Re: git: uh-oh |
Previous Message | David Fetter | 2010-08-20 20:37:30 | Re: Version Numbering |