The 12/11/09, Daniele Segato wrote: > On Wed, Nov 11, 2009 at 8:24 PM, Nicolas Sebrecht <nicolas.s.dev@xxxxxx> wrote: > > The 11/11/09, Daniele Segato wrote: > > > > If you want to track changes of settings in a per-production-repo basis, > > you should do it _out_ of your main development repository. The latter > > should have a publishable template instead (eg. "user = user_login", > > "password = set_your_password"). > > you are probably right but even if I place this files outside my > repository I still have to modify them manually.. I don't understand. You'll still have to manually these files regardless _how_ they are tracked. > it's the same of having them into the repo but in .gitignore When I say, "out of the main development repository", I don't think "out of the directory of the repository" but "out of the tracking git system". I think you should look at 'git subtree' or 'git submodule' to track the setting files out of the _main_ repository and _inside_ the main development directory. > we are customizing a third party product and I can't change the way it > is build up. > > I don't think that this situation is so uncommon anyway. Yeah, it doesn't help to be unable to do everything we want! But I'm pretty sure git can do something very convenient in your case. -- Nicolas Sebrecht -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html