On 25 October 2011 11:24, 3quid <[email protected]> wrote: > Thanks Colin. That solved it, although I swear I already tried to do > it like that!
Use a version control system (probably git) for controlling your code, and commit often. Then you can always look back and see exactly what you have tried. Do experimental stuff on a branch so you can easily chuck it away if it does not work, or merge it in if it does. > Your help is much appreciated. Glad to be of help Colin -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
