Re: git: uh-oh
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Max Bowsher <maxb@f2s.com>, Magnus Hagander <magnus@hagander.net>, Michael Haggerty <mhagger@alum.mit.edu>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2010-08-20T20:39:32Z
Lists: pgsql-hackers
On Fri, Aug 20, 2010 at 4:27 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Max Bowsher <maxb@f2s.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