Re: tracking file locally without pushing it to remote

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Jul 23, 2011, 12:35 UTC
Message-ID: <CACsJy8AaDj3QV-unj80cY4x18tHRDAr0hdgtiRuCs6SCYP33ng@mail.gmail.com>
In-Reply-To: <CACsJy8BZSWaaNPjQYKXmTHvJ5vbNXBfNCtV78DUJVDuPqtp1Hg@mail.gmail.com>

On Sat, Jul 23, 2011 at 7:27 PM, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:

> Manage the configuration files in a different repository (but with the
> same working tree). Git does not support sharing worktree this way, so
> it's a bit inconvenient.

And if you still want to manage config template files with the same name in the main repository, to be pushed to a remote one. Set assume-unchanged bit (see update-index man page) on those files in main repo, so you won't see their changes against the templates and "git commit -a" won't commit them. To be on the safe side, add a post-commit hook that disallows committing any changes to config files.

Assume unchanged bits are not persistent (ie. you will need to set it after branch switching, reset index...), but if this way works well, maybe we can add a pattern file to automatically set it.

-- 
Duy