Re: Git migration

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Git migration
Date: 2013-04-16 16:54:29
Message-ID: 20130416165428.GK8626@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Heikki Linnakangas wrote:
> On 16.04.2013 17:03, Alvaro Herrera wrote:
> >Heikki Linnakangas wrote:

> >>Some non-empty manufactured commits still remain, but that's ok.
> >
> >Yeah, there are only two of them and they look pretty harmless.
>
> There's a few more than that:

Ah. I only looked for those in branches and forgot about tags. These
ones:

> commit 48261b56e4728384bc8b57ab4f3b9ca17cf0126c
> Author: cvs2svn <cvs2svn>
> Date: Fri Jan 6 21:36:59 2006 +0000

> commit 9dd9f238f0f3e33e04e7db1ab5bc9ac13a9ad1fe
> Author: cvs2svn <cvs2svn>
> Date: Wed Feb 22 15:12:35 2006 +0000

> commit 61f9d8e6743a4f2cf535a59757495189ee0a66c2
> Author: cvs2svn <cvs2svn>
> Date: Fri Sep 21 06:36:28 2007 +0000

> I'm not sure why we end up with these, but I'm happy to leave them
> like that.

They look a bit like rewinding the history to get rid of certain files
in the tags. Maybe it'd be easy to add the tags to those files so that
they don't have to be removed at all? However, they are not large
removals so probably not a big deal.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Heikki Linnakangas 2013-04-17 13:46:52 Re: Git migration
Previous Message Heikki Linnakangas 2013-04-16 16:10:11 Re: Git migration