Re: Moving to git
От | Maciek Sakrejda |
---|---|
Тема | Re: Moving to git |
Дата | |
Msg-id | CAH_hXRZ4p+Tax7Mi4TCfccJ3wYbdT-2EzUzdGMDv7z29C-E6QQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Moving to git (Craig Ringer <ringerc@ringerc.id.au>) |
Ответы |
Re: Moving to git
Re: Moving to git |
Список | 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
В списке pgsql-jdbc по дате отправления: