Re: Handling non-git config files

Git-list,

Thanks to Jon, Ian and Tim for your replies.

I was reading Jon's reply and the workflow he uses seems to fit my purpose. To migrate an application, you would branch it, set any local configuration and commit. To bring over any changes you would just merge them over. This would leave any deployment artifacts (a great term to describe local changes) intact.

I have only been using branching and merging since November, when I was instructed how to do so by git-list. I realise now that this is just basic branching and merging. The workflow described will work with any SCM software that supports branching and merging.

Richard