From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Brandon Casey <casey@nrlssc.navy.mil>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Teach fsck and prune about the new location of temporary objects
Date: Thu, 24 Jul 2008 23:07:50 -0700 [thread overview]
Message-ID: <7vd4l2xzrd.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0807250233031.4140@eeepc-johanness> (Johannes Schindelin's message of "Fri, 25 Jul 2008 02:33:52 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Thu, 24 Jul 2008, Brandon Casey wrote:
>
>> Since 5723fe7e, temporary objects are now created in their final destination
>> directories, rather than in .git/objects/. Teach fsck to recognize and
>> ignore the temporary objects it encounters,
>
> It somehow feels wrong for fsck to ignore anything that could be used.
Back when we created temporaries in .git/objects/, these tmp_obj files
were not even checked nor looked at, because fsck_object_dir() checked
only those 256 fan-out directories, so this is nothing new.
And these tmp_obj files are something we _expect_ to be in the object
directory. The user can ^C out object creation codepath anytime, and we
do not reference the final destination objects from refs nor the index to
preserve the integrity of the repository when that happens. In other
words, they are crufts, but they are not something unusual nor get alarmed
about.
And it also is the right thing to do to remove them in prune.
next prev parent reply other threads:[~2008-07-25 6:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 22:41 [PATCH] Teach fsck and prune about the new location of temporary objects Brandon Casey
2008-07-25 0:33 ` Johannes Schindelin
2008-07-25 6:07 ` Junio C Hamano [this message]
2008-07-27 2:33 ` [PATCH] fsck: Don't require tmp_obj_ file names are 14 bytes in length Shawn O. Pearce
2008-07-27 4:15 ` Junio C Hamano
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=7vd4l2xzrd.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=casey@nrlssc.navy.mil \
--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).