From: walt <wa1ter@myrealbox.com>
To: git@vger.kernel.org
Subject: Empty temp files in the .git/objects subdirectories
Date: Thu, 03 Nov 2005 16:56:58 -0800 [thread overview]
Message-ID: <dkebkq$ova$1@sea.gmane.org> (raw)
I've noticed (sometimes) after using cg-update to
pull from Linus's kernel tree, that I have multiple
empty files named *.temp in the various subdirectories
of .git/objects/.
These *.temp files don't exist in Linus's repository
on kernel.org, so I am assuming they must be created
locally at my end by either cogito or git (dunno which).
They cause no problems except for annoying warning
messages, for example, while doing a git-fsck-*.
I'm using git and cogito(HEAD), both updated by using
cg-update from their git repositories on kernel.org,
so I'm current up to the very last minute :o)
Any suggestions how I can discover who is leaving
behind all these spurious empty *.temp files?
next reply other threads:[~2005-11-04 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 0:56 walt [this message]
2005-11-04 1:54 ` Empty temp files in the .git/objects subdirectories Nick Hengeveld
2005-11-04 2:32 ` 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='dkebkq$ova$1@sea.gmane.org' \
--to=wa1ter@myrealbox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.