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

Re: test git conversion

From: Maciek Sakrejda <msakrejda(at)truviso(dot)com>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Kreen <markokr(at)gmail(dot)com>, Dave Cramer <pg(at)fastcrypt(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: test git conversion
Date: 2012-01-24 18:05:50
Message-ID: CAH_hXRaUr_jXLYDu6QoON5muyG_dvprnMu1Sez-u9F0drauH0A@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
>> It looks like the same set of changes was committed to both trunk and
>> the branch, and nothing else ever happened on that branch. You're
>> saying that we should just drop that branch point and have the git
>> branch point at f44a35... (see gist linked above) as a stub branch
>> (that is, a branch with no commits of its own), yes?
>
> Yes.

Done. I think the only remaining thing is the keyword cleanup. I
presume what I suggested before works (keep keyword expansion as it
was in CVS; do a cleanup commit in git in all active branches to purge
expandable keywords; I believe this is what the main project did)? I
took out the "grep -v"s from the tag verification script to see what
was there, and there are some subtantial diffs around that. I tried
tweaking the cvs2git config, but that only gives different diffs. I
need to spend more time looking at this, but I should be done soon
(though if anyone has any insight here, I welcome it).

---
Maciek Sakrejda | System Architect | Truviso

1065 E. Hillsdale Blvd., Suite 215
Foster City, CA 94404
(650) 242-3500 Main
www.truviso.com

In response to

Responses

pgsql-jdbc by date

Next:From: Kris JurkaDate: 2012-01-25 07:38:31
Subject: GIT move
Previous:From: Kris JurkaDate: 2012-01-24 17:54:50
Subject: Re: Java 1.4

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