From: "J. Bruce Fields" <bfields@fieldses.org>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, git@vger.kernel.org
Subject: Re: why git-reset needed after "cp -a" of a git repo?
Date: Wed, 22 Aug 2007 16:14:35 -0400 [thread overview]
Message-ID: <20070822201435.GK20946@fieldses.org> (raw)
In-Reply-To: <200708221919.l7MJJNkX012184@agora.fsl.cs.sunysb.edu>
On Wed, Aug 22, 2007 at 03:19:23PM -0400, Erez Zadok wrote:
> Thanks for the info and tips. It's a good idea of course to detect any
> possible changes, but I wonder if for those of us who know what they're
> doing (i.e., living on the edge :-), there could be an option to ignore
> inode numbers and just depend on good 'ol ctime/mtime (as other tools like
> make do).
I don't think there's any need for that. You can always just run
git-update-index --refresh or just git-status to refresh the stat data
that's kept in the index. That miscellaneous stat data (ctime, mtime,
inode number) is just there as an optimization, so git-diff doesn't have
to read every file. It can be tossed out and regenerated any time.
--b.
prev parent reply other threads:[~2007-08-22 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 18:57 why git-reset needed after "cp -a" of a git repo? Erez Zadok
2007-08-22 19:04 ` Jon Loeliger
2007-08-22 19:11 ` Linus Torvalds
2007-08-22 19:19 ` Erez Zadok
2007-08-22 20:14 ` J. Bruce Fields [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=20070822201435.GK20946@fieldses.org \
--to=bfields@fieldses.org \
--cc=ezk@cs.sunysb.edu \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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).