FYI, there is a great system to do access control called gitolite. It is
used on kernel.org. It could help keep things sane until the transition
is very sane :)
Marc-André Laverdière
Software Security Scientist
Innovation Labs, Tata Consultancy Services
Hyderabad, India
On 10/03/2011 08:02 AM, 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
>
