From: Marc Zonzon <marc.zonzon+git@gmail.com>
To: git@vger.kernel.org
Subject: git-relink status (or bug?)
Date: Sat, 21 Jun 2008 12:36:36 +0200 [thread overview]
Message-ID: <20080621103636.GA696@kernoel.dyndns.org> (raw)
When trying to use git-relink, I found it quite disappointing when
going over packs. Git relink seem to make the assumption that there is
a unique mapping from object name to object identity, which is of
course acceptable for loose objects that are named with their sha-1
but false for .pack and .idx, to pack objects with the same name have
contains the same objects but may be not packed in the same order, or
compression.
Moreover .idx files can not be considered alone, but depends on the
associated .pack.
When it happen that you have two different packs with the same name
but of different sizes, git relink does not hard link the .packs
because the size differ, and hard link the idx. And your repository is
corrupted.
It happen when you clone a repository, repack the clone and relink the
clone to the original one.
I found very few information about git relink, but as it appears in
changelog of v1.5.4 I suppose it is not obsoleted.
What about the use of this script?
Marc
next reply other threads:[~2008-06-21 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 10:36 Marc Zonzon [this message]
2008-06-21 19:22 ` git-relink status (or bug?) Junio C Hamano
2008-06-21 20:23 ` marc zonzon
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=20080621103636.GA696@kernoel.dyndns.org \
--to=marc.zonzon+git@gmail.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).