I don't think it'll be that much of a problem... other than the occasional svn:externals reference, most recent installations should be via Gem anyway, which won't be affected. If it does become an issue, I'll just suck it up and add a post-push hook to commit stable changes to Subversion as well.
Since m_r is typically installed via script/plugin, I don't think we'll be switching it over. - Nathan Tom Stuart wrote: > On 11 Feb 2008, at 00:43, Nathan Weizenbaum wrote: > >> I'm not sure what to do if >> you're tracking stable or a particular tag, though... I don't really >> want to continually sync with the subversion repo. At that point, it >> might just be a good idea to use the gems. >> > > This is a pretty grim scenario; I can already see many hours of git-vs- > svn-vs-gems hassle unfolding in my future. Rails developers > overwhelmingly use svn. Please don't switch make_resourceful over too. > I agree that distributed version control is the future, and starting > new projects on git is fun for everyone, but taking existing ones > completely out of svn and into git only generates headaches for > existing users. > > Cheers, > -Tom > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
