git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Tomas Carnecky <tom@dbservice.com>
Cc: Maaartin <grajcar1@seznam.cz>, git@vger.kernel.org
Subject: Re: Forcing re-reading files with unchanged stats
Date: Wed, 12 Jan 2011 22:32:18 -0500	[thread overview]
Message-ID: <20110113033217.GA32661@sigill.intra.peff.net> (raw)
In-Reply-To: <4D2E6D99.9060907@dbservice.com>

On Thu, Jan 13, 2011 at 04:12:25AM +0100, Tomas Carnecky wrote:

>  On 1/12/11 3:07 PM, Maaartin wrote:
> >There are files in my working tree which changes, but their size and mtime
> >remains the same (I know it's strange, but it's useful). Can I make git to re-
> 
> When can this be useful?
> 
> >read them all, so it recognizes the change? Ideally, using a configuration
> >variable. The repo is fairly small, so speed is no issue here.
> 
> Try git update-index --refresh. I'm not aware of any config option,
> but you might want to look through man git-config.

That won't work, as it respects the stat information. So does
--really-refresh. AFAIK, there isn't a way to tell update-index to
ignore start information, short of blowing away the index entirely, and
doing a read-tree to repopulate it.

I'm curious what this use case is, and whether it would be acceptable to
update something like ctime on the files to make them stat-dirty to git.

-Peff

  reply	other threads:[~2011-01-13  3:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 14:07 Forcing re-reading files with unchanged stats Maaartin
2011-01-13  3:12 ` Tomas Carnecky
2011-01-13  3:32   ` Jeff King [this message]
2011-01-13  7:26     ` Junio C Hamano
2011-01-14 21:03     ` Maaartin-1

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=20110113033217.GA32661@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=grajcar1@seznam.cz \
    --cc=tom@dbservice.com \
    /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).