mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Viet Nguyen <>
To: Igor Djordjevic <>,
Subject: Re: Add feature to stop tracking files while keeping them in the index
Date: Wed, 22 Nov 2017 00:16:30 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Igor,

On November 20, 2017 at 7:15:00 PM, Igor Djordjevic
( wrote:
> Hi Viet,
> On 20/11/2017 10:52, Viet Nguyen wrote:
> > Currently, a file can be either tracked or untracked. So, I propose we
> > add a feature to stop tracking files while keeping them in the index.
> >
> > Example scenario:
> > - A developer would like to add some configuration files with example
> > values, e.g. DB_PASSWORD=changeme. But in the future he also want to
> > update those files and to notify the others with conflicts.
> If I`m understanding you correctly, what you want should already be
> possible through `git update-index --[no-]skip-worktree`[1].
> Regards, Buga
> [1]

We are currently using git-update-index in a client hook, but found it
a little tedious because sometime we forget to configure the hooks
correctly and it just stop working. So I am thinking that it would be
a lot better if we can store it somewhere in the shared repository, so
the other developers could ignore the fact that some files in our
project are special and treat them just like the regular files.

Best regards,


      reply	other threads:[~2017-11-22  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20  9:52 Add feature to stop tracking files while keeping them in the index Viet Nguyen
2017-11-20 17:13 ` Igor Djordjevic
2017-11-22  8:16   ` Viet Nguyen [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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).