From: Johannes Sixt <j.sixt@viscovery.net>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, git-dev@github.com,
"Shawn O. Pearce" <spearce@spearce.org>,
Nicolas Pitre <nico@fluxnic.net>
Subject: Re: [PATCH] pack-objects: protect against disappearing packs
Date: Fri, 14 Oct 2011 16:35:23 +0200 [thread overview]
Message-ID: <4E9848AB.3010802@viscovery.net> (raw)
In-Reply-To: <20111014130703.GB7808@sigill.intra.peff.net>
Am 10/14/2011 15:07, schrieb Jeff King:
> Within a single process, I don't think so. This change impacts only
> pack-objects, which always runs as a separate process, and never deletes
> packs itself. The most likely problematic code path would be "git
> repack -d", but it waits for pack-objects to complete successfully
> before removing any packs.
Thanks. The test suite didn't find any issues on Windows.
-- Hannes
next prev parent reply other threads:[~2011-10-14 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 1:23 [PATCH] pack-objects: protect against disappearing packs Jeff King
2011-10-14 1:31 ` Jeff King
2011-10-14 2:43 ` Nicolas Pitre
2011-10-14 2:42 ` Nicolas Pitre
2011-10-14 13:02 ` Jeff King
2011-10-14 7:06 ` Johannes Sixt
2011-10-14 13:07 ` Jeff King
2011-10-14 14:35 ` Johannes Sixt [this message]
2011-10-14 18:03 ` [PATCH 1/2] " Jeff King
2011-10-14 18:04 ` [PATCH 2/2] downgrade "packfile cannot be accessed" errors to warnings Jeff King
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=4E9848AB.3010802@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git-dev@github.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=peff@peff.net \
--cc=spearce@spearce.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.