From: Daniele Segato <daniele.bilug@gmail.com>
Date: Thu, 12 Nov 2009 09:29:46 GMT
Subject: Re: Locally manage user/branch setting files without pushing them remotely
Message-ID: <9accb4400911120129h54609846jac9eb3b6cb07b792@mail.gmail.com>
In-Reply-To: <20091111192449.GH27518@vidovic>

On Wed, Nov 11, 2009 at 8:24 PM, Nicolas Sebrecht <nicolas.s.dev@gmx.fr> wrote:
> This looks to _not_ be a piece of the development project. Settings used
> for the tests suites, company where you work, etc _are_ clones (from the
> abstract POV, at least) of the maintainer public repository.
>
> 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..
it's the same of having them into the repo but in .gitignore

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.

Regards,
Daniele