From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Daniele Segato <daniele.bilug@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Subject: Re: Locally manage user/branch setting files without pushing them remotely
Date: Wed, 11 Nov 2009 20:24:49 +0100 [thread overview]
Message-ID: <20091111192449.GH27518@vidovic> (raw)
In-Reply-To: <9accb4400911110401g5c44d011u50cafcfe736a2ec6@mail.gmail.com>
The 11/11/09, Daniele Segato wrote:
> The project has a lot of setting that are really binded to the user
> and should not go pushed in a remote repository (example: database
> connections parameters / filesystem paths)
> We have a .template file for those settings but the actual settings
> are really binded to the user environment.
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").
--
Nicolas Sebrecht
next prev parent reply other threads:[~2009-11-11 19:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 12:01 Locally manage user/branch setting files without pushing them remotely Daniele Segato
2009-11-11 12:14 ` Yann Simon
2009-11-11 13:00 ` Daniele Segato
2009-11-11 13:06 ` Yann Simon
2009-11-11 13:46 ` Paolo Ciarrocchi
2009-11-11 19:24 ` Nicolas Sebrecht [this message]
[not found] ` <9accb4400911120118t3257a1n6f2a05abb1008c8@mail.gmail.com>
2009-11-12 9:29 ` Daniele Segato
2009-11-12 9:31 ` Nicolas Sebrecht
2009-11-12 10:13 ` Daniele Segato
2009-11-12 11:15 ` Nicolas Sebrecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091111192449.GH27518@vidovic \
--to=nicolas.s.dev@gmx.fr \
--cc=daniele.bilug@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).