Hi,
Sorry for being a bit in a rush. My name is Kjetil Nygård, and I'm a
norwegian. My strongest and weakest attribute is my impatience.
I have seen the discussion about moving to git.postgresql.org and/or
github. But there it stalled as far as I see. That's why I dared to
shoot from the hip.
My proposal is this:
1. Do a git cvsimport.
2. Upload it to git.postgresql / github.
When it comes to the concrete elements you mention, I would go for the
simple solution. Namely just do an import, and upload it. Then fix
problems as they occur.
Authorship is preserved with git-cvsimport. The authors could maybe have
been updated to username@somewhere.com, but I would not say it is very
important. I guess that people will understand who jurka is anyway.
About keyword-expansion I don't have any experience. (We just ignored it
when we migrated from cvs to svn / git.)
Empty folders should not be a problem. They can and should be made by
the ant script anyway.
So my proposal is to follow Nike and "Just do it!"
PS: It's just a proposal.
-Kny :-)
On Sun, 2011-10-02 at 19:32 -0700, Maciek Sakrejda wrote:
> 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