From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
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 16:20:09 +1200 [thread overview]
Message-ID: <46a038f90706192120q6c64a854re589f27b3bdbc0d5@mail.gmail.com> (raw)
In-Reply-To: <46a038f90706192117x53420c04o27f05e8fa6c338a5@mail.gmail.com>
On 6/20/07, Martin Langhoff <martin.langhoff@gmail.com> wrote:
> > But because you push to a local repository (a mounted USB stick is
> > considered a local repo) then you don't get to negociate the pack
> > capabilities of the final destination, and therefore more "bad" delta
> > objects might sneak in again.
>
> How does that work? So any repo we push _from_ can override (and muck
> up) the destination repo, ignoring its config?
>
> That sounds a bit broken - the pack being built for a local
> destination should respect the settings of the destination repo.
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.
cheers,
m
next prev parent reply other threads:[~2007-06-20 4:20 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 [this message]
2007-06-20 5:14 ` Nicolas Pitre
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=46a038f90706192120q6c64a854re589f27b3bdbc0d5@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=jonathan.newman@catalyst.net.nz \
--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).