From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Cc: Daniele Segato <daniele.bilug@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Locally manage user/branch setting files without pushing them remotely
Date: Thu, 12 Nov 2009 10:31:46 +0100 [thread overview]
Message-ID: <20091112093146.GB25398@vidovic> (raw)
In-Reply-To: <9accb4400911120129h54609846jac9eb3b6cb07b792@mail.gmail.com>
The 12/11/09, Daniele Segato wrote:
> On Wed, Nov 11, 2009 at 8:24 PM, Nicolas Sebrecht <nicolas.s.dev@gmx.fr> 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
next prev parent reply other threads:[~2009-11-12 9:32 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
[not found] ` <9accb4400911120118t3257a1n6f2a05abb1008c8@mail.gmail.com>
2009-11-12 9:29 ` Daniele Segato
2009-11-12 9:31 ` Nicolas Sebrecht [this message]
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=20091112093146.GB25398@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).