From: Kevin <compufreak@gmail.com>
To: Arup Rakshit <aruprakshit@rocketmail.com>
Cc: git@vger.kernel.org
Subject: Re: git pull not ignoring the file which has been sent to the temporary ignore list
Date: Sat, 24 Jan 2015 12:03:41 +0100 [thread overview]
Message-ID: <20150124110341.GA15090@vps892.directvps.nl> (raw)
In-Reply-To: <1557175.bcUxN10iZq@linux-wzza.site>
On Sat, Jan 24, 2015 at 10:20:46AM +0630, Arup Rakshit wrote:
> On Friday, January 23, 2015 01:14:03 PM you wrote:
>
> [..]
>
> There are some configuration files, like `database.yml`, where we
> generally put our local DB credentials and we don't want to share such
> things. That's why we always put related settings inside the
> .gitignore file. But while I will change it, git will not track the
> changes of the file, but .gitignore. That's why I used the first
> thread command. But when the time the came to take a `git pull`, I got
> to know about the mess. What should be the ideal decision in this case
> ?
>
In an ideal sittuation, configuration data is not stored inside git,
because this would tie the code only to one environment.
So what you would store in git is a template of the configuration data,
that can be used to create the actual config file that is used.
This way, you don't have any problems with having to change tracked
files only for you local environment.
prev parent reply other threads:[~2015-01-24 11:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 18:27 git pull not ignoring the file which has been sent to the temporary ignore list Arup Rakshit
2015-01-23 19:31 ` Junio C Hamano
2015-01-23 18:35 ` Arup Rakshit
2015-01-23 20:12 ` Stefan Beller
2015-01-23 21:14 ` Junio C Hamano
2015-01-23 21:38 ` Stefan Beller
2015-01-23 22:26 ` Junio C Hamano
2015-01-23 22:32 ` Stefan Beller
2015-01-24 3:50 ` Arup Rakshit
2015-01-24 11:03 ` Kevin [this message]
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=20150124110341.GA15090@vps892.directvps.nl \
--to=compufreak@gmail.com \
--cc=aruprakshit@rocketmail.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).