From: Erik Mouw <erik@harddisk-recovery.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Andreas Ericsson <ae@op5.se>, git@vger.kernel.org
Subject: Re: Safe way to remove .temp objects?
Date: Fri, 27 Jan 2006 11:14:33 +0100 [thread overview]
Message-ID: <20060127101433.GB3673@harddisk-recovery.com> (raw)
In-Reply-To: <7v1wyvfa8p.fsf@assigned-by-dhcp.cox.net>
On Thu, Jan 26, 2006 at 04:24:06AM -0800, Junio C Hamano wrote:
> What is being asked is not about loose objects but droppings
> commit walkers make when interrupted.
That's indeed what I meant.
> I think *.temp files are garbage and you can safely remove
> them. They are not even correct objects.
It looks like it was safe to remove, all git commands I tried just
work.
Thanks,
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
prev parent reply other threads:[~2006-01-27 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 9:35 Safe way to remove .temp objects? Erik Mouw
2006-01-26 11:18 ` Andreas Ericsson
2006-01-26 12:24 ` Junio C Hamano
2006-01-27 10:14 ` Erik Mouw [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=20060127101433.GB3673@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).