git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David Tweed" <david.tweed@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: ok for git to delete temporary packs on write error?
Date: Wed, 28 Nov 2007 15:48:36 +0000	[thread overview]
Message-ID: <e1dab3980711280748s53bf23f4j11be8c0472b7a216@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.99999.0711281000590.9605@xanadu.home>

On Nov 28, 2007 3:01 PM, Nicolas Pitre <nico@cam.org> wrote:
> On Wed, 28 Nov 2007, David Tweed wrote:
>
> > Hi, I'd like to check if there's any reason in the overall design of
> > git which would make deleting tmp_pack's that have suffered
> > write errors a bad idea? (Before I look further into this I may be missing
> > a good reason why they shouldn't be auto-deleted.)
[snip]
> I'd suggest they get removed a part of the prune command.

Mmm, I hadn't looked at the source and spotted the prune
is actually a separate process to the repack. From a policy
POV is it ok to assume any tmp_pack*'s existing when
prune is run can be deleted? (I know you're not supposed
to be having any other git ops going on whilst git gc works.)

Now I know they aren't being kept around for, say, "emergency
error recovery" I may look to see if I can come up with
an acceptable patch. (Don't hold your breath waiting.)

-- 
cheers, dave tweed__________________________
david.tweed@gmail.com
Rm 124, School of Systems Engineering, University of Reading.
"we had no idea that when we added templates we were adding a Turing-
complete compile-time language." -- C++ standardisation committee

      reply	other threads:[~2007-11-28 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28  7:42 ok for git to delete temporary packs on write error? David Tweed
2007-11-28 15:01 ` Nicolas Pitre
2007-11-28 15:48   ` David Tweed [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=e1dab3980711280748s53bf23f4j11be8c0472b7a216@mail.gmail.com \
    --to=david.tweed@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=nico@cam.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).