If we do end up using GitHub, it'll automatically publish the master branch (what used to be trunk) to Subversion. 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.
Of course, you could always set up your own git-svn repo and sync it yourself. Yay for distribution! - Nathan Tim Carey-Smith wrote: > * s.ross <[EMAIL PROTECTED]> [2008-02-10 16:00:09 -0800]: > > >> Only one concern. I have a bunch of projects that reference haml using >> svn:externals. Most Rails plugins are on svn so a wholesale changeover >> to git would be (for me) premature. Is there some kind of bridge that >> will help with this? >> > > I would suggest that the stable versions of haml be pushed out to svn > without the commit history. That way people can still track the library > using svn:externals. > > Anyone wanting to develop on the library should really use the primary > version control system (in this case, git). > > Just a thought, > Tim > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
