On Tue, Aug 5, 2008 at 11:04 AM, Kevin Tew <[EMAIL PROTECTED]> wrote: > Git is really nice for: > local branches,
This is on par with svk... > frequently(daily) rebasing local branches to keep in sync with HEAD, How does this work? What's the pain threshold? > publishing local branches for others to review, Is this something that we'd host near the svn repository? On a machine like feather? Wherever a developer wanted? (How would we advertise?) > allowing non-committers to make changes and publish those changes > publicly So, like patches in RT, but closer to the 'metal', as it were? > Kevin > > Will Coleda wrote: >> >> Using svn as a backing store, how can we more easily work with long >> lived branches? >> >> I've some existing branches which are long lived, and doing the svn >> merge either way is extremely slow. >> >> I know much of our community used svk for a while; I think the usage >> there has dropped off as git is the new shiny. My usage of svk was for >> local branching; I couldn't easily share my work in progress with the >> community. >> >> Does anyone have *any* recommendations? (including: you're doing the >> merge wrong). >> >> I'm bccing the current svn admins to find out if they have any ideas as >> well. >> >> Would an upgrade on the server side to 1.5 help with performance? (It >> would certainly make the maintenance aspect of the merging less >> painful.) >> >> > > -- Will "Coke" Coleda
