From: Walter Bright <boost@digitalmars.com>
To: git@vger.kernel.org
Subject: Re: noob user, want checkins to all be forced to LF terminated lines
Date: Fri, 30 Jul 2010 23:24:34 -0700 [thread overview]
Message-ID: <i30fj8$cit$1@dough.gmane.org> (raw)
In-Reply-To: <20100731055735.GA19812@LK-Perkele-V2.elisa-laajakaista.fi>
Ilari Liusvaara wrote:
> On Fri, Jul 30, 2010 at 10:45:36PM -0700, Walter Bright wrote:
>
>>> [1] But upon restore, the working copy cache will be wrong
>> Why? Is it someplace else?
>
> It is inside .git directory and will be caught by full recursive
> backup. Unfortunately, it contains i-node numbers, which aren't
> preserved through backup and restore.
>
> The wrong i-node numbers would then confuse git (false positives
> in modification detection). Fortunately, this data can be rebuilt
> with single command (see below).
Hmm. One thing I wanted to get away from from Windows was the inability to
restore files by just copying the tree.
>>> and needs to be rebuilt (git update-index --refresh).
That's crucial to know. Thanks!
next prev parent reply other threads:[~2010-07-31 6:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 4:23 noob user, want checkins to all be forced to LF terminated lines Walter Bright
2010-07-31 4:49 ` Jonathan Nieder
2010-07-31 5:14 ` Walter Bright
2010-07-31 5:39 ` Ilari Liusvaara
2010-07-31 5:45 ` Walter Bright
2010-07-31 5:57 ` Ilari Liusvaara
2010-07-31 6:24 ` Walter Bright [this message]
2010-07-31 15:12 ` David Aguilar
2010-07-31 5:44 ` Jonathan Nieder
2010-07-31 6:32 ` Walter Bright
2010-07-31 6:41 ` Ilari Liusvaara
2010-07-31 20:38 ` Jonathan Nieder
2010-07-31 20:51 ` Walter Bright
2010-08-03 23:56 ` Jay Soffian
2010-08-04 5:29 ` Will Palmer
2010-07-31 5:41 ` Miles Bader
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='i30fj8$cit$1@dough.gmane.org' \
--to=boost@digitalmars.com \
--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 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).