> http://rails.lighthouseapp.com/projects/8994/tickets/1-since-r9244-migrations-broken-on-clean-db
> As for git branches vs git patches, we're still experimenting a > little on that. On the above ticket I did both. From a submitter's POV it's easier to just attach a patch. But, raising the the bar to forking rails, and creating a branch, (which is not really that hard) might be something you want to do. > pulling from someone's branch has the advantage that > it's pretty easy to do, but it doesn't give us anything nice like > 'signed off by' or stuff like that. > > What do you guys think? 'git apply' is also pretty easy to do. I presume that the core team will be applying patches, and editing commit messages in the centralised repo style for the master branch. In which case git patches seem like the way to go. Cheers, Ian -- Argument from Design--We build web applications Western House 239 Western Road Sheffield S10 1LE UK Mobile: +44 (0)797 4678409 | Office: +44 (0)114 2667712 <http://www.ardes.com/> | <http://blog.ardes.com/ian> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
