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:12:39 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.99.0706200102380.20596@xanadu.home> (raw)
In-Reply-To: <46a038f90706192117x53420c04o27f05e8fa6c338a5@mail.gmail.com>
On Wed, 20 Jun 2007, Martin Langhoff wrote:
> On 6/20/07, Nicolas Pitre <nico@cam.org> 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.
But it does! The problem is that _you_ are cheating it by removing the
USB stick and mounting it somewhere else.
Then you're using cogito which bypasses things.
If you use pure git on the client machine, and actually use git-pull or
git-fetch _without_ the -l switch then validation of the updated data
will occur and there would be no way to muck up the destination repo.
Nicolas
next prev parent reply other threads:[~2007-06-20 5:12 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
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 [this message]
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.0706200102380.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).