From: Jonathan Nieder <jrnieder@gmail.com>
To: Bostjan Skufca <bostjan@a2o.si>
Cc: git@vger.kernel.org
Subject: Re: Configurable filename for what is now .gitignore
Date: Fri, 29 Aug 2014 22:43:12 -0700 [thread overview]
Message-ID: <20140830054312.GA28512@google.com> (raw)
In-Reply-To: <CAEp_DRDCQqkwL1N-PemLtOvPEv-xfBW4MatAOomwi+my9QeK8g@mail.gmail.com>
Hi,
Bostjan Skufca wrote:
> Git is great for tracking code development, but when deploying
> mentioned code by using git itself, various configuration files must
> be created additionally, which are normally .gitignored, for various
> reasons (code portability, sensitive data, etc). There is currently no
> simple way of tracking changes to those critical configuration files
> (at least none that I am aware of).
>
> One way to approach this would be tracking those changes in separate
> git repository.
Have you seen zit
<https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools#Zit>?
Curious,
Jonathan
next prev parent reply other threads:[~2014-08-30 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-30 3:33 Configurable filename for what is now .gitignore Bostjan Skufca
2014-08-30 5:43 ` Jonathan Nieder [this message]
2014-08-31 1:55 ` Bostjan Skufca
2014-09-01 20:30 ` Bostjan Skufca
2014-09-01 23:33 ` Duy Nguyen
2014-09-04 20:33 ` Bostjan Skufca
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=20140830054312.GA28512@google.com \
--to=jrnieder@gmail.com \
--cc=bostjan@a2o.si \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.