From: Johannes Sixt <j.sixt@viscovery.net>
To: Sergio <sergio.callegari@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Some information that git diff saves and that git status does not
Date: Tue, 09 Mar 2010 07:35:47 +0100 [thread overview]
Message-ID: <4B95EC43.2040705@viscovery.net> (raw)
In-Reply-To: <7vpr3emr3s.fsf@alter.siamese.dyndns.org>
Junio C Hamano schrieb:
> I didn't fully read what you wrote but after you copy a repository from
> one to another outside git (be it done with unison or rsync), you should
> run "update-index --refresh".
And the reason for this is that git also looks at the inode numbers, and I
guess that unison does not go as far as to preserve them between machines...
-- Hannes
next prev parent reply other threads:[~2010-03-09 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 10:46 Some information that git diff saves and that git status does not Sergio
2010-03-08 21:38 ` Junio C Hamano
2010-03-09 6:35 ` Johannes Sixt [this message]
2010-03-09 6:56 ` Junio C Hamano
2010-03-09 6:58 ` Sergio Callegari
2010-03-09 8:20 ` Dmitry Potapov
2010-03-08 21:52 ` Jens Lehmann
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=4B95EC43.2040705@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sergio.callegari@gmail.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).