Skip site navigation (1) Skip section navigation (2)

Re: Moving to git

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Maciek Sakrejda <msakrejda(at)truviso(dot)com>
Cc: Kjetil Nygård <polpot78(at)gmail(dot)com>, Kris Jurka <books(at)ejurka(dot)com>, Marko Kreen <markokr(at)gmail(dot)com>, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Moving to git
Date: 2011-10-12 15:28:11
Message-ID: CADK3HHLdZs+NBaAZOG1SK6ubEYkHR1QBQBz+wU4Dwh9D6aZ77w@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
On Sat, Oct 8, 2011 at 3:06 PM, Maciek Sakrejda <msakrejda(at)truviso(dot)com> wrote:
>> PS: Does it really matter if the history is a bit altered by the
>> conversion process? As long as HEAD and the tags are the same?
>
> I think we can tolerate some minor discrepancies, but we do want
>
> 1. Diff-free HEAD, tags, and tips of branches
> 2. A sensible-looking development history that represents more or less
> what happened in CVS
>
> If we only pay attention to (1), we lose too much information, since,
> e.g., development history can be critical in determining when a bug
> was introduced and what releases it affects.
>
>> The history could be kept in a read-only cvs-repository :-)
>
> Or we could keep a git mirror and you submit patches that are applied
> to the CVS repo, which you then pull into your repo through
> git-cvsimport once they're committed. There are all sorts of technical
> tricks we can play, but I think the goal is to minimize that, and
> essentially have a git repo representing the entire development
> history as if pgjdbc had been using git from day one.
>
> ---
> Maciek Sakrejda | System Architect | Truviso
>
> 1065 E. Hillsdale Blvd., Suite 215
> Foster City, CA 94404
> (650) 242-3500 Main
> www.truviso.com
>



Are we at a state where this is workable ?

Dave

In response to

Responses

pgsql-jdbc by date

Next:From: Kjetil NygårdDate: 2011-10-14 18:41:45
Subject: Re: Moving to git
Previous:From: Laurian VostinarDate: 2011-10-12 14:03:41
Subject: BUG #6253: JDBC driver: getIndexInfo() returns quotes around quoted column names

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group