Re: Moving to git

From: Maciek Sakrejda <msakrejda(at)truviso(dot)com>
To: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
Cc: Kjetil <polpot78(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Moving to git
Date: 2011-10-03 02:32:13
Message-ID: CAH_hXRZ4p+Tax7Mi4TCfccJ3wYbdT-2EzUzdGMDv7z29C-E6QQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

For what it's worth, I'll second this, although Dave's right--the post
is a little presumptuous. Having worked on a number of svn-to-git
transitions, the mechanics of preserving history are actually pretty
trivial (git cvsimport / git svn clone make this dead easy), but doing
the right thing with commit authorship, keyword expansion, empty
folders, etc. is much trickier. And if you *don't* do that right off
the bat, the entire "lineage" changes when you correct it later,
making merges a nightmare (if you do them naively in this situation,
you end up with two alternate timelines in the same repo). The
transition needs to be done right (rather than running `git cvsimport`
and throwing the result up on github).
---
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

Browse pgsql-jdbc by date

  From Date Subject
Next Message Marc-André Laverdière 2011-10-03 04:21:04 Re: Moving to git
Previous Message Dave Cramer 2011-10-03 01:59:44 Re: Moving to git