From: Nicolas Pitre <nico@cam.org>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>, jonathan.newman@catalyst.net.nz
Subject: Re: Debugging strange "corrupt pack" errors on SuSE 9
Date: Wed, 20 Jun 2007 01:14:48 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.99.0706200113020.20596@xanadu.home> (raw)
In-Reply-To: <46a038f90706192120q6c64a854re589f27b3bdbc0d5@mail.gmail.com>
On Wed, 20 Jun 2007, Martin Langhoff wrote:
> OTOH, as a workaround, it _should_ work if I force a repack on the
> usb-repo after each push, right? It'll wear the USB disk out, waste
> human+cpu time and kill some kittens along the way, but it'll do for
> the time being.
Right. And you don't need to use -f with git-repack for it to work.
Nicolas
next prev parent reply other threads:[~2007-06-20 5:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 2:36 Debugging strange "corrupt pack" errors on SuSE 9 Martin Langhoff
2007-06-20 3:33 ` Nicolas Pitre
2007-06-20 4:17 ` Martin Langhoff
2007-06-20 4:20 ` Martin Langhoff
2007-06-20 5:14 ` Nicolas Pitre [this message]
2007-06-20 5:01 ` Nicolas Pitre
2007-06-20 5:10 ` Martin Langhoff
2007-06-20 5:17 ` Nicolas Pitre
2007-06-20 5:12 ` Nicolas Pitre
2007-06-20 8:46 ` Jakub Narebski
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=alpine.LFD.0.99.0706200113020.20596@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=jonathan.newman@catalyst.net.nz \
--cc=martin.langhoff@gmail.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).