From: Junio C Hamano <junkio@cox.net>
To: Nick Hengeveld <nickh@reactrix.com>
Cc: git@vger.kernel.org
Subject: Re: Empty temp files in the .git/objects subdirectories
Date: Thu, 03 Nov 2005 18:32:54 -0800 [thread overview]
Message-ID: <7vvez95ei1.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051104015452.GB3001@reactrix.com> (Nick Hengeveld's message of "Thu, 3 Nov 2005 17:54:52 -0800")
Nick Hengeveld <nickh@reactrix.com> writes:
> These are created by git-http-fetch to hold data as it's being
> fetch from the remote repository. They are left behind after a transfer
> error so that the next time git-http-fetch runs it can pick up where it
> left off. If they're empty though, it would make more sense to delete
> them rather than leaving them behind for the next attempt.
That makes sense. Thanks.
prev parent reply other threads:[~2005-11-04 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 0:56 Empty temp files in the .git/objects subdirectories walt
2005-11-04 1:54 ` Nick Hengeveld
2005-11-04 2:32 ` Junio C Hamano [this message]
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=7vvez95ei1.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=nickh@reactrix.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).